james

Hi Ace, there is only 1 nic. I thought that the EventID
articles were great. The 7062 prompted me to set-up a
reverse look-up zone which got rid of my black hole error
and I have looked at the cache.dns as well as the root
hints to ensure that I am not looking at myself but my
7062 error is still occuring a dozen times daily and the
5781 is once a day. I think these must be related to
themselves and the fact that the dcdiag always fails the
connectivity test (attached)

Just as a curiosity, why do the root hints only go from A
to M and not the entire alphabet?

Thanks for your assistance.
James

Testing server: Default-First-Site-Name\DOMAINCONTROLLE
Starting test: Connectivity
The host c396d75f-13ab-4e35-94e0-
2c45bc739f6c._msdcs.fashionmark.com co
uld not be resolved to anIP address. Check the DNS
server, DHCP, server name, etc
Although the Guid DNS name
(c396d75f-13ab-4e35-94e0-
2c45bc739f6c._msdcs.fashionmark.com) couldn't
be resolved, the server name
(domaincontroller.fashionmark.com)
resolved to the IP address (192.168.1.21) and was
pingable. Check that the IP address is registered
correctly with the DNS server.
......................... DOMAINCONTROLLE failed
test Connectivity


86806C5286C8@microsoft.com,

thoughts, then I


Should I try

server name too


NetBIOS name. This will

since as a host

configuration?

benefit.

ace fekay [mvp]

In news:079701c3c372$50eec820$a101280a@phx.gbl,
James <anonymous@discussions.microsoft.com> posted their thoughts, then I
offered mine

Because there are only 13 of them.

This is strange that you are still getting these errors. In your nameserver
tab, do they show your current DNS server name and IP in there?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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

ace fekay [mvp]

In news:079701c3c372$50eec820$a101280a@phx.gbl,
James <anonymous@discussions.microsoft.com> posted their thoughts, then I
offered mine


<snip>

Tell you what, let's try this to refresh the SRV records.

1. Delete the \system32\config\netlogon.dns and netlogon.dnb files
2. Restart the netlogon service

If this doesn't help, assuming this zone is AD Integrated, change it to a
Primary, rerun the above and let me know what you get.

Maybe, just maybe, it may have something to do with the name, but not
entirely sure since I've never encountered a scenario where the NetBIOS name
gets truncated due to length, where you may have entered the full NetBIOS
name (DOMAINCONTROLLER) when you created the machine, but got truncated to
DOMAINCONTROLLE.

If you do an nbtstat -n, what name shows up in the result?

Do you have another server to install DNS on by chance, just to get it off
this machine for a swing method? What I mean is install DNS on another
machine, create a secondary zone of your zone, let the transfer happen, then
change it to a Primary, point your DC to this machine and see if that makes
a difference. If the errors clear up, then I would suggest to uninstall DNS
on the machine, restart, then reinstall it (make sure you reapply the SP or
use an SP integrated i386 source).

Hope that helps

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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