[address-policy-wg] PI for Not-DNS Anycast.
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jørgen Hovland
jorgen at hovland.cx
Wed Aug 8 15:12:52 CEST 2007
-----Original Message----- From: Greg L. [mailto:bgp2 at linuxadmin.org] > To speed up DNS queries for their customers and clients. If I was running DNS hosting service I would prefer to have Australian visitors querying DNS boxes in Australia. ... I can't get myself to agree with you on that, but I understand the problem. If you actually have customers in Australia, TTL will take care of that for you. If you only have a few customers it cannot possibly be that important to have slightly lower latency for your domain at the first query. (FYI we are a medium size dns hosting company) > If I was running DNS hosting service I would prefer to have Australian visitors querying DNS boxes in Australia. Clients from Germany querying anycast node in Germany. And if I was in Romania, all local clients to "hit" DNS anycast IP in Romania. Sure thing, but you probably mean the closest DNS box network wise/AS-hop/latency, not by country. > Why should only ccTLD's They shouldn't. > and some large LIR's Large LIRs probably have a decent network and can do what they want within their own network. Do you disagree that they should have that advantage? >..allowed to lower the service query latency for DNS traffic and sometimes cut the bandwidth bills? Cheers, j
- Previous message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
- Next message (by thread): [address-policy-wg] PI for Not-DNS Anycast.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]