event 5774

  • Thread starter Thread starter Derrick
  • Start date Start date
D

Derrick

i received this error message when my Win2K server is
starting up. the description is:

registration of the DNS record '_ldap.tcp.d1d6eaef-6762-
43d7-bdb0-ebe80bb1fd01.domains._msdcs.bas.com 600 IN SRV
0 100 389 email.bas.com' failed with the following error:
DNS server unable to interpret format.

this is only one of the messages, in fact, all other srv
records found in my dns is all shown with the same
errors. anyone know what is going on? please advise. i
been trying all night....

cheers,
derrick
 
In
Derrick said:
i received this error message when my Win2K server is
starting up. the description is:

registration of the DNS record '_ldap.tcp.d1d6eaef-6762-
43d7-bdb0-ebe80bb1fd01.domains._msdcs.bas.com 600 IN SRV
0 100 389 email.bas.com' failed with the following error:
DNS server unable to interpret format.

this is only one of the messages, in fact, all other srv
records found in my dns is all shown with the same
errors. anyone know what is going on? please advise. i
been trying all night....

cheers,
derrick
Click to expand...

This *usually* means you're using your ISP's DNS in your machines IP
properties. It's trying to register into their server and they're not
allowing it, which 99% of ISPs don't anyway.

Recommended guidelines:
Point all machines in an AD infrastructure only to your own internal DNS
server(s) that are authorative for the AD zone. If you need Internet
resolution, configure a Forwarder. If the Forwarding option is grayed out,
delete your root zone. Both are shown how to here:
http://support.microsoft.com/?id=300202
This way all machines will ask your AD DNS first and if it doesn't have the
answer, it will "forward" it to your ISP's DNS and proivide the answer to
your client. This ensures AD will function properly.

More info about AD and DNS:
http://support.microsoft.com/?id=291382

Now if I'm incorrect in my guess here, please provide us with a little more
info that will really help us out to diagnose this, such as:

1. Unedited ipconfig /all
2. AD DNS domain name (as it shows up in your ADUC)
3. The DNS domain name as it's spelled in DNS.
3. If updates are set to at least YES on the zone properties.

This would really help out.
Thanks

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top