We help IT Professionals succeed at work.

Windows DNS Not Replciating

techmiss
techmiss asked
on
Hi All,

I have built another domain controller that is in a new site, I have two existing domain controllers in another site.

I have noticed that new forward lookup zones for the domain are not replicating to the new Domain Controller, I can only see one error for DNS which is below, but this was on 9th November so I can't see it being an issue.

How do I force replication / troubleshoot this problem?

(New & and an existing DNS Server is Win Server 2008 R2 Standard, other server is Win 2003 R2 Standard).

Cheers

K
Event Type:	Warning
Event Source:	DNS
Event Category:	None
Event ID:	4013
Date:		09/11/2011
Time:		16:12:36
User:		N/A
Computer:	VSVR-RD-DC-05.domain.local
Description:
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

Comment
Watch Question

Krzysztof PytkoSenior Active Directory Engineer
Top Expert 2012

Commented:
You DNS is AD-Integrated and it's replicated over RPC like AD database. Please check if your DNS zone on that new DC has the same serial number. If so, it was replicated, DC needed just some time to finish replication

Regards,
Krzysztof

Author

Commented:
Each DC has a different serial number under SOA in DNS, in increments of 1.

The server has been built for a long time so I would have expected it to have replicated by now (many weeks ago).

Is it possible that sites and services have not been configured correctly?

Thanks
K
Senior Active Directory Engineer
Top Expert 2012
Commented:
OK, so please run in command-line on your DC

dcdiag /e /c /v >c:\dcdiag.log

and attach this file here for analyze, please. We will see what could be a reason

Do you have any firewall between DCs? Yes, it might be also related with AD Sites and Services configuration

Krzysztof

Author

Commented:
Hi, is attached,

It is possible that the replication has not been correctly configured in Sites & Services but I do not know.

K

 dcdiag.log
Krzysztof PytkoSenior Active Directory Engineer
Top Expert 2012
Commented:
OK, that's really strange because DCDIAG doesn't show serious errors for DC-05

There were problem with SYSVOL/NETLOGON replication but after some time it was replicated. However the SYSVOL replication problem is still on DC-ONE, maybe this is an issue?

Can you verify if your SYSVOL/NETLOGOn on DC-ONE are up-to-date, please?

Krzysztof
Is the new server found in the Zone Nameservers?

Open DNS management, right click on the zone, properties, Name servers tab.

Author

Commented:
Hi All,

How can I verify that sysvol is up to date... I am indeed getting file replication errors but I have been through several MS KB articles and all seems well on my servers.

@simonlimon, yes the servers are all listed as DNS servers in the zone.

Cheers

K

Author

Commented:
Assisted in getting to the problem, but did not 100% solve.

Thanks

K