Dynamic DNS not working

[Guest]

Dynamic DNS updates is set to YES, but replication between my local DC's are
not working.

Error: “The DSA operation is unable to proceed because of a DNS lookup
failureâ€

When I restart the netlogon service of a DC, i get the following error:
"Event ID: 5773
Description: The DNS server for this DC does not support dynamic DNS. Add
the DNS records from the file SystemRoot%\System32\Config\netlogon.dns' to
the DNS server serving the domain referenced in that file."

It seems as if Dynamic DNS (DDNS) is not working properly?

 

[Kevin D. Goodknecht Sr. [MVP]]

Dynamic DNS updates is set to YES, but replication between my local
DC's are not working.

Error: "The DSA operation is unable to proceed because of a DNS lookup
failure"

When I restart the netlogon service of a DC, i get the following
error: "Event ID: 5773
Description: The DNS server for this DC does not support dynamic DNS.
Add the DNS records from the file
SystemRoot%\System32\Config\netlogon.dns' to the DNS server serving
the domain referenced in that file."

It seems as if Dynamic DNS (DDNS) is not working properly?

Can you post the ipconfig /all from the DC, the AD Domain name, and the list
of zones in DNS?

 

[Ryan Hanisco]

Hello!

You need to make sure that all of your DCs can find the appropriate srv
records in the DNS. A good place to start is using PINGs. It's not a
direct as NSLOOKUP, but it will make sure you are seeing exactly what
the DC is when querying -- Jjust make sure you don't have a firewall or
something like that blocking ICMP.

What you want to do is PING the domain's FQDN from each DC. If you do
not get a return from the PDCe, you are definitely having a DNS problem.

From there, start using NSLOOKUP and IPCONFIG /all to track down which
DNS server and zone is the problem.

Also, if you are not AD integrating your DNS, you will want to consider
this. There are a lot of benefits and a few possible caveats, but it is
generally advisable for Internal DNS.

Finally, if you have CAs in your environment and are requiring signing
between DCs or secure DNS updates, a problem with the CA or certificate
chain can cause this.

Send on the information Kevin was asking for and we can go from there.

Best Regards,

Ryan Hanisco