Correctly Setting up DNS on remote sites

Ok I have one main site and 2 remote offices. Each site has its own dhcp server. Main Site :10.32.2.x Remote Site #!-10.32.3.x remote site #2-10.32.4.x . All these are nt4.0 servers, I am in the process of planing the 2003 migration. At my main office i have a dns zone(insurance.com) that is being updated dynamiclly with the dhcp server. At the 2 remote offcies I need to ensure that they each have there own dns servers and dhcp servers. Can i just creat a standard zone for each office and have it replicate to the other dns servers or do I have to have a seperate zone for each sub net? Thanks
LVL 2
uyhtAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
JammyPakConnect With a Mentor Commented:
in other words, configure all 3 DHCP servers with the main site's DNS server as their primary, and this should work.
0
 
JammyPakCommented:
if all of the machines are in the same Active Directory domain (insurance.com) then you should setup DNS servers in the remote sites as secondary's to the primary DNS server in the main site.
0
 
JammyPakCommented:
sorry...I re-read your post, and you said you're migrating to Win2K3...I assumed you were running a domain. If you're running Active Directory, then you're less flexible, since domains will now be integrated with DNS (going from NT4 to 2003). If you don't have AD, then you could do it either way...one big domain, or 3 little domains. The only real "disadvantage" of one domain is that the updates would have to be written to the primary server and then zone transferred to the secondaries - so there'd be some time delay (minor) and also more WAN traffic since everyone's going to be updating the primary (unless your WAN links are close to saturation, this shouldn't really be a big deal. The main disadvantage I can see of 3 domains is just the manangement of it. You'd want to put all the domain suffixes in the search list of each pc....because otherwise the person has to know - gee, I want to connect to server1...is that server1.domaina.com, server1.domainb.com, or server1.domainc.com? Makes things much simpler to just have the one domain suffix to deal with. (IMO)
0
 
uyhtAuthor Commented:
ok but if dhcp is assigning addresses at the remote sites can I point that dhcp server back to the primary dns server even though it is handing out different subnet addresses.

As I understand it, you are saying, Main office Primary DNS server remote offices have secondary dns servers that update from the primry and the dhcp servers at the remote office contact the primary to update it with current lease information for all scopes. Is this doable?
0
 
JammyPakCommented:
DNS can certainly handle dynamically registering addresses from different subnets, that's not a problem.

the DHCP server will send the DNS updates to the DNS server(s) that it is configured to use - so, if you make the primary DNS server (the one at the main site) the primary DNS server for the DHCP server (in the ip properties of the network connection) then that's the server it  will send the registration updates to. the way I read it (haven't confirmed this with a sniffer), the DHCP server sends the updates to all DNS servers configured for any of  it's network connections that are active. of course, only the authoritative server (primary, not slave) can update the zone, so that one should really be the primary server (first one to try) that the DHCP server is set to use.
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.