Link to home
Start Free TrialLog in
Avatar of MoonLive
MoonLive

asked on

DNS Record Manupluation

Hi,
I have one DNS server at each remote location. Each DNS server sync with main office DNS server.
I would like to create A record that point to different server base on the location of office. And not overwrite when DNS sync.

For example,
Server1         A       192.168.10.1  in  OfficeA DNS
Server1            A       192.168.13.1  in  OfficeB DNS
Server1            A       192.168.16.1       in  OfficeC DNS

Purpose of this is for when user access server1, the DNS always point to local server instead of Main OfficeA server whenever the user access the server1 from different location.

Is that possible?
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

No  and it would be unwise to do so. Did should always be a single source of authority. Use clustering, load balancing, or similar to get clients to their closest server. But that server would still be globally unique on DNS.
Each DNS should point to itself first for answers, then say Site A for things not locally stored, but what you're asking is dns suicide
Avatar of MoonLive
MoonLive

ASKER

Cliff, Let me clarify if this make sense. The actual server name is unique for each location.
Server1         A       192.168.10.1  in  OfficeA DNS -->FS1
Server1            A       192.168.13.1  in  OfficeB DNS --> FS2
Server1            A       192.168.16.1       in  OfficeC DNS --> FS3

I created CNAME to point the server. Is still not recommend?  
Thanks for your quick answer.
Natty, Some expert saying that DNS should point to other DNS when you have more than one DNS and other like you saying point to itself. I don't know which one is correct.
Does it work, if it does then leave it as configured, however do you have a back dns setup should one fail you'll have dns nightmares especially troubleshooting it remotely, you will have to be on site to fix.
Everyone has their own opinion I was taught to look to self first its always faster to do, and whatever else self can not answer is forwarded to somewhere else for answers. now if I'm using something else as the main and it broke and let say it was remotely how do i fix, self can be fixed easily---- hey i like less headaches do you?
Natty, yes i do have a 2nd DNS server that works. But my question for this post is about  the same CNAME for each location point to different server base on the location without the CNAME .
Perhaps I do not understand the question but...

If you create AD sites with correct subnets linked to sites, irrespective if a DC exist in site, any resource that is AD site aware (like DFS) will use the local source
ASKER CERTIFIED SOLUTION
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If you configure something like this, any client that queries OfficeA's DNS server will resolve Server1 to 192.168.10.1, any client that queries OfficeB's DNS server will resolve Server1 to 192.168.13.1, and any client that queries OfficeC's DNS server will resolve Server1 to 192.168.16.1.

However...

Assuming these records are all in the same zone, that zone is likely going to be replicated among all three DNS servers. If that's the case, this isn't going to work. Also, are the clients at each office configured to only use that local office's DNS server? If they're configured to use another office's server as an alternate, there's a chance they're going to resolve that name to the wrong address.
Thanks for all of you. I got the idea that this is not possible.  Even if there is way to do, it is not something I want to pursue. I don't like to be complicate the situation. I am currently using DFS to work out and works good, but i was looking for another alternative way to make it work.