DNS Replication between DC and Non-DC

I have two DNS Servers one Win2k the Other Win2k3.  Both were domain controllers with DNS.  I DCPROMO demoted the Win2k server and the DNS zones went with it.  I am looking to retain the Win2k machine as a DNS Server just not a DC.  How can I get the Win2k machine to be part of the DNS replication?  There are currently no Zones Showing on the Win2k DNS.  
robanomAsked:
Who is Participating?
 
Wonko_the_SaneCommented:
You will have to setup the DNS zones as "secondary zones" on the non-DC. Note that this will be read-only copies, so clients cannot dynamically update their IP if they use this DNS server, it would merely provide redundancy for the existing DNS zones.
0
 
arnoldCommented:
On your DC make sure that the AD zone is not limited to domain controllers. Properties of the Domain Zone change the Replication to make sure it replicates to all DNS servers in the AD domain.
Make sure that you have an AD-Integrated zone.
on the win2k it should appear once refreshed.
Though not sure why you chose to demote the win2k perhaps your only DC backup. You should have at least two DCs since that is where user/computer/gpo/etc is.  If you only have one and it experiences hw failure, you will be in a ......
0
 
robanomAuthor Commented:
I have two win2k3 domain controllers however the other win2k3 dc I do not want to be a DNS Server.  
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Wonko_the_SaneCommented:
You will need to use secondary zones. AD replication only works to domain controllers. This is by design, since it's stored in the directory. A member server has no directory, and therefore you can't replicate to it.
0
 
Wonko_the_SaneCommented:
And really, your best choice would be to make your second DC a DNS server, it's just easier. Please note that AD does not function without DNS at all, and not making your second DC a DNS server could affect your redundancy. Of course I don't know your reasoning about not making it a DNS server, but I would advice you to do this only if you have really good reasons for that.
0
 
robanomAuthor Commented:
This was exactly what I was looking for
0
 
robanomAuthor Commented:
The other DC is also an Exchange box, I know against best practice.  that is the reason I do not want to setup DNS on that machine as well.
0
 
Wonko_the_SaneCommented:
DNS is such a leight-weight, stable and low-footprint service that it woulnd't hurt. Your big issue is Exchange & AD on the same box as you already mentioned, and adding DNS is really harmless. Ultimately your decision, but IMHO you are better off with just adding DNS as well. And it can be removed with the click of a button.
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.