Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows Server 2003 - DNS

Status
Not open for further replies.

desmondkan

IS-IT--Management
Dec 20, 2007
10
US
HI,

I have a Windows Server 2003 box which has 2-NICs as a backup domain controller and secondary DNS. One of the NIC has a static ip address of 192.168.2.1 and the other one has a static ip address of 10.50.1.4. For some reasons it doesn't pass the "forward" test but it passed the rest when I ran dcdiag /test:dns. Does any one know why and how to fix it??

Another question, does anyone know the correct way to COPY AND AUTOMATIC UPDATE all the dns records from primary dns server to secondary dns server?

any input will be appreciated. Thank you.
 
For your second question, is this is Active Directory DNS you would need to have set your DNS as AD integrated when doing DCPROMO for your secondary domain controller. Any changes/updates would then propagate to your secondary DNS and vice versa.

Here's a good how-to on how to do it correctly.

 
Hi hanoirocks,

Thanks for your reply. I didn't set the DNS option when I promoted it to be a backup domain controller. Do you know if there's a way to propagate the DNS after promoting it? Thank you.

Desmond
 
Well you can do it manually or you can convert your existing to AD Integrated.

Here's how -
Manual:

If you want to do it manually. Select properties on your forward and reverse zones. Add your name secondary name server computer. Then go to the "Zone Transfers" Tab select "allow zone transfers" to only those listed on the name servers tab.
 
hanoirocks,

Thanks for your replies.

There are two types of zones in my primary DNS server which I need to propagate to the secondary DNS server. I don't have any problem with the primary zone because it's already AD-integrated in my primary DNS server but the secondary zone are the ones that don't propagate. I can't change the secondary zone to the AD-integrated zone otherwise I would ruin the relationship/structure. So I am guessing the manual way is the only choice for my situation ?

Thanks.

Desmond
 
Both my Forward and Reverse zones propagate with my AD integrated.

When you created the zone, was it a forward primary or secondary?

I once created another primary zone for "Intranet" purpose and it propagated to the other server within 10 minutes. That is because it gives you the option of storing the zone in AD.
My understanding of the secondary zones is that it is for importing the zone from another server. Is that what you are trying to do? If that's the case I think you'd have to setup the zone transfer manually.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top