Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have multiple offices in other countries that egress out of one location. The problem is that the DNS replies are being resolved for that country as opposed to the country the user is actually in.

Example: user does a request for google, and gets, when I would like them to get because the user doing the search is in Germany. Make sense?

We are using Microsoft DNS. is there a way to do this?

share|improve this question

Yeah, set the egress point back to their local offices instead of centralizing it.

Otherwise, not really. Geolocation isn't embedded into DNS requests, or "tagged," as such. Google (for example) gets a request from a client, looks up the originating IP and then matches that up against a geo-ip database to determine what country that client is in, and redirects it appropriately. As that process is entirely out of your control, on systems you don't own, you can't really do anything about it, short of making sure the originating IP of your clients is actually located where they are.

You could maybe use Group Policy or proxy settings to manage groups of users so that the German ones go to and the Spanish ones go to, and so on, by basically forcibly re-redirecting them or explicitly directing to instead of, but you'd have to do that for every domain that does geographically-based redirects or checks, which would probably be a rather large pain in the ass. Certainly seems better to me to just let traffic exit from each office location than forcing it to exit from a central one.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.