I'm
having a problem somewhat similar to Steve's. For some reason my AD-integrated
DNS lost it's AD zones (I have a suspicion why, that's another thread). This is
not the first time and in the past I could run netdiag /fix and all would be
well with the world. That's no longer working.
AD
Name == homedom.dc-resources.net == DNS zone (note: tried with a top-level of
dc-resources.net and a child of homedom as well as one zone called
homedom.dc-resources.net)
It is
not disjointed (properties on My Computer, Network Ident., server name ==
wolfpack.homedom.dc-resources.net, domain ==
homedome.dc-resources.net)
in top
level of my domain the SRV records of SOA, NS and A for the server itself
exist
Allow
dynamic updates == yes (unsecured)
DNS
servers in TCP stack == itself first (have tried with and w/o ISP's DNS listed,
no difference)
There
is no "." zone
I am
logged on as Ghod (from domain admin to DNS admin, tried three different
accounts)
Manually created the zones (_msdcs, etc), still no go
Went
through the checklist at http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp
Since
it's only one server I _could_ recreate all the records manually, but
dang it, this _should_ be doable without having to resort to that. MSKB dances
all around the issue eventually ending up with running netdiag
/fix.
Any
ideas?
|
Title: Message