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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS Problem

Status
Not open for further replies.

rphips

IS-IT--Management
Sep 12, 2003
590
US
I just flushed my DNS and I am recieving the following errors in my event viewer

Registration of the DNS record (all of the SRVs) 600 in srv 0 100 3268 gues-pdc,gues.com failed with the following error
DNS server unable to interpret format

help what does this mean and can it be fixed.

rphips
 
From a newsgroup post: "There could be many reasons for this event. I got this error because our HQ uses a BIND DNS. Some people fixed this by deleting the problem record by hand and restart the NETLOGON service."

Error: "DNS server unable to interpret format." - This error message may be generated in several circumstances. See Q259277 for a general approach on troubleshooting this. In some cases this may be caused by the security setting on the parent.local server being set to only use secure updates. Changing this to allow "dynamic updates" (instead of only secure) might eliminate the problem.

Another newsgroup discussion thread suggested that the event was caused by the fact that the Active Directory Domain Controller running the DNS server did NOT point to itself as a DNS server (instead it used the ISP DNS servers). Changing the DNS server settings to point to itseld fixed the problem.

Error: "A socket operation was attempted to an unreachable host." - Apparently, the DNS server is not reachable. This could be due to network problems (cables, hubs, etc...) or the server may be down (or the IP address changed). Verify that there is connectivity between the computer reporting the problem and the DNS servers where is trying to register.

Error: "DNS RR set that ought not exist, does exist.". As per Microsoft, when the Netlogon service tries to register the GUID record in the _msdcs.forestrootzone, the GUID record may not be registered if there is an MX record that is wildcard character (*). The Netlogon service does a DNS query of type ALL for the guid._msdcs.forestrootzone. If a wildcard record exists, the DNS server responds to the query with the MX server information and the dynamic update does not succeed. See Q325208.

You can also check Q284963
 
the news group fix was the reason thanks alot and stars to you Chris77504

rphips
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top