cjewett
asked on
Setting up DNS on additional domain controller
I have 3 locations and have setup additional domain controllers at the remote sites to keep some of the traffic to a minimum over the WAN link. I have followed the instructions on my previous post https://www.experts-exchange.com/questions/21828243/2003-servers-at-remote-sites.html but still a little confused on how the DNS works. I have promoted the new server in the subnet of the remote location and setup the new site in Sites and Services. Will all authentication now occur locally on that subnet? I also installed DNS on the new server but didnt know if I needed to setup a new Forward Lookup Zone or replicate from the domain controller at the other site? Is there a setting I need to change on the DNS server at the main site? Please help.
Yes, authentication will occur locally if you setup a site and associated the subnet for that site to it.
On the main site, make sure the zones are AD Integrated. That's all.
When DNS is installed on another DC it will automatically create and populate the zones from the main site.
No other work on this is required other than creating the Reverse Lookup zone for the new subnet. This only needs to be done on one DNS server then replication will take care of the rest.
If you do not see any zones building up on the remote site then there is something wrong with the communication between it and the main site.
Let us know.
On the main site, make sure the zones are AD Integrated. That's all.
When DNS is installed on another DC it will automatically create and populate the zones from the main site.
No other work on this is required other than creating the Reverse Lookup zone for the new subnet. This only needs to be done on one DNS server then replication will take care of the rest.
If you do not see any zones building up on the remote site then there is something wrong with the communication between it and the main site.
Let us know.
ASKER
I have talked with one of my peers and they said that configuring this additional domain controller as a Secondary Name Server was not the proper way to do this (Which I think you are saying as well). According to him you should just be able to install DNS and it will replicate from the other DC. When I install DNS on this DC all the reverse lookup appear but not the forward lookup zones. I reversed the changes I made in the KB article and uninstalled and reinstalled DNS on the second DC, made sure the the zones are AD integrated on the primary but they still dont populate. So I dont have to add a forward lookup zone on the secondary? Dont know what Im doing wrong.
Is replication working properly?
It takes a little while if it's in a remote site.
It takes a little while if it's in a remote site.
ASKER
I rebooted the remote server and they finally appeared. After the reboot I was getting Event ID 5774 several times. I did a little research and ended up adding the primary DC IP in the seconday DNS on this server and rebooted to test and the message went away. Is this normal to have to add the IP of the primary DC in the secondary DNS?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER