Anycast method alternative for geo-based DNS servers

I've read about the 'Anycast' approach, this is what I understand so far:
1. A client queries a domain name, it receives a list of the domain's name servers, and their IPs from the roots
2. The client now chooses one name server IP randomly, and queries it for the domain name
3. The 'anycast' method routes this request to the nearest name server available, based on the origin of the client

Now I'm trying to understand the alternative to Anycast, this is what I think happens:
1. A client queries a domain name, it receives a list of the domain's name servers, and their IPs from the roots
2. The client now chooses one name server IP randomly and queries it for the domain name
3. There is no geo-decision while selecting the name server, but the name server serves the results according to a geographic location of the client's origin.

A. Am I accurate?
B. There is no way of serving a different name server, geo-based, other than Anycast?

Thanks,
Lubster
LVL 4
LubsterAsked:
Who is Participating?
 
expert1010Connect With a Mentor Commented:
A) Not really. Anycast is when you have several DNSs placed in different geographic places (or at least in different places routing wise) but with the same IP-number for all of them. This means that you will go to the nearest (again, routing wise) DNS. Load sharing if you like.

B) There is other approaches. GeoDNS comes to mind. But you have to know more about your world around you not just standard DNS. Things such as routing, coordinates and stuff. One is the way Akamai do it. They use BGP and some other magic to find closest server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.