DNS Replication

[Emyeu]

Below shows the error when i run 'netdiag' on server2. No problem when run
on server1.
How can i resolve this problem?

DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not registered correctly on
DNS se
rver 'SERVER1'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS se
rver 'SERVER2'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.

 

[James Raines]

Hello,

Thank you for choosing Microsoft and for using our Newsgroups. I have
reviewed the information you have provided this far. My understanding of
the issue is the following:

You have 2 DC's, Server1 and Server2. When you run netdiag on Server2 it
shows that the DNS records aren't registered properly.

CAUSE
=====

This is generally caused by:

1) The server isn't pointed to a proper DNS server in the TCP/IP properties
on the NIC.
2) The DHCP client service isn't running. This service is required to
register DNS records.
3) The DNS zone isn't configured for dynamic updates. If this is the case
you will need to manually create the SRV and Host records for the DC which
isn't recommended.
3) The NIC isn't configured to register it's records in DNS.

These are the general causes for your issue.


RESOLUTION:
============

Based on your problem description it looks like both DC's are DNS servers.
For troubleshooting purposes I would point both DC's to Server1 only for
DNS in the TCP/IP properties of thier NIC's.
At that point, restart the netlogon service on both DC's. This will attempt
to re-register the SRV records.
Then from a command prompt type the following commands on both DC's

ipconfig /flushdns <emter>
ipconfig /regisiterdns <enter>

This will flush the dns cache on the servers and re-register the Host
records.
After this re-run netdiag on Server2 and see if your problem persists.

If the issue is gone please follow this article on setting up DNS when you
have multiple DNS servers in your domain:

275278 DNS Server Becomes an Island When a Domain Controller Points to
Itself
http://support.microsoft.com/?id=275278


Best Regards,

James Raines
Microsoft Corporation

 

[Emyeu]

I tried the methods you mentioned below. It doesn't resolved the problem.
The connectivity between both DC1 & DC2 are okay.
Any advice?

 

[ptwilliams]

If you followed James' advice and restarted netlogon when both DCs DNS
client (TCP/IP\ Advanced\ DNS) were configured to point at DC1 (the primary
if you are not running AD-Integrated) and the appropriate SRV records
haven't been registered, check to ensure that you have the DHCP Client
Service set to automatically start and currently running on both DCs. Also
check that the DNS zone is configured to accept dynamic updates.

* Note. The DHCP client service needs to be running even on machines
with statically defined TCP/IP settings, as it is used by Netlogon to
register DNS records dynamically.

You may also want to flush the DNS event log after doing this before you
rerun dcdiag/ netdiag.


--

Paul Williams

http://www.msresource.net
http://forums.msresource.net


I tried the methods you mentioned below. It doesn't resolved the problem.
The connectivity between both DC1 & DC2 are okay.
Any advice?