How can I make DNS resolve different addresses dependant on location?

I have a domino web-enabled database located in mutliple location.
The documents replicate on a schedule so content is always up-to-date.
We use replicas on each site, mainly because some locations cannot procure fast Internet connections to allow everyone to use one central server.

As all sites are in one windows domain, they share DNS.
The dilemma I face is that I want anybody to be able to visit the address (database.domain.com) and be directed to their site's local server.
For Example;
a Russia uses visits to database.domain.com and the site on10.53.0.5 opens
while a user in Bahrain  visits database.domain.com and the site on10.50.0.5 opens
etc...

So far I haven't found a solution inside DNS to set-up these dynamic resolutions....
UnifraxAsked:
Who is Participating?
 
DrDave242Connect With a Mentor Commented:
At this time, Windows DNS has no built-in mechanism for this. I can only think of one way to make it work. It's a little bit kludgy, but it should do the job:

Assuming database.domain.com is the FQDN you want to use, create separate forward lookup zones named database.domain.com on the DNS servers in each site. Don't make these AD-integrated zones, and don't set up any zone transfers from one site to another, as you don't want the zones replicating between sites. (Zone transfers between DNS servers within a site are fine.) In each zone, create blank host records with the IP addresses of the corresponding database.domain.com servers within that site.

With this arrangement, users in each site should only be able to resolve database.domain.com to the IP addresses of the servers within that site. In my experience, if you have a zone named database.domain.com containing a blank host record and also have a zone named domain.com which contains a host record named database, the blank host record in the database.domain.com zone is the one whose IP address will be returned in response to a query. You may want to test this a bit before deploying it in production, though.

EDIT: Of course, this assumes that each site has at least one DNS server. If this isn't the case, I can't think of a way to make it work within Windows DNS.
0
 
UnifraxAuthor Commented:
This worked perfectly. Thanks!
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.