• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 312
  • Last Modified:

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 http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21828243.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.
0
cjewett
Asked:
cjewett
  • 3
  • 3
1 Solution
 
cjewettAuthor Commented:
I think I may have found the answer to my own question in Microsoft KB 816518.  Dont know if thats the correct answer or not just updating everyone.
0
 
Netman66Commented:
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.
0
 
cjewettAuthor Commented:
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.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
Netman66Commented:
Is replication working properly?

It takes a little while if it's in a remote site.

0
 
cjewettAuthor Commented:
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?
0
 
Netman66Commented:
Normally you would, yes.  Your new server would throw a few errors until it had all the records - thus the secondary would be used in the meantime.

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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now