Replicating server DNS zone has no contents.

[dany2010]

Hi,

 

Just promoted a server to replicate the main DC and everythings seems ok apart from the DNS.

 

When looking at the zones from the second server the DNS zones show no content like it hasnt been replicated at all but when i connect to the server from server one (adding second server into server 1 management console) it shows server 2 has all the computers listed.

 

Is this normal behavour?

 

Thanks

[Geoff]

Is this an AD integrated DNS zone?

[dany2010]

It is yeah. Just un integrated and re-integrated but still the same.

[glennda]

if you right click and select force reload from master does it appear? On the primary dc does the secondary appear as a name server?

 

What is the secondary dc set to in terms of its own DNS settings within IP info?

 

Is there any firewalls turned on?

[Geoff]

Any replication issues? (check the event logs)

[dany2010]

Hi,

 

Yes Windows firewall is used on both servers.

 

In the nameservers tab both servers appear

 

Primary Server network setting:

Primary DNS = Secondary server

Alternate DNS = Primary Server

 

Second server network settings:

Primary DNS = Primary Server

Alternate DNS = Second server

 

 

 

Repadmin /showreps show replications completed successfully but in the log:

 

dns service error 4013

 

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

[Geoff]

That's caused by a deadlock when you reboot both servers together. They try and query each other for DNS so they can start AD (which contains the DNS information). This Catch-22 results in about a 20min apparent hang on bootup before you can login.

[dany2010]

THanks,

 

Have changed the server so the primary dns points to themselves rather than each other but still no joy.

 

Could the deadlock be caused by something else?

 

If i add server 1 onto server 2 dns MMC i cant see any entries on server 1.

If i add server 2 onto server 1 dns MMC i can see everything on both servers.

 

THis isnt to do with the FSMO roles is it?

Edited December 11, 2012 by dany2010

[Geoff]

What happens when you troubleshoot with nslookup?

[dany2010]

Just trying

Nslookup server2

And

Nslookup server 1

 

I don't get any errors.

 

That's about all I know about Nslookup tho.

 

We have noticed some workstations have the wrong ip address against their DNS name.