J
JC
any ideas why a DC , NOT running DNS, would get this warning ?
JC said:any ideas why a DC , NOT running DNS, would get this warning ?
JC said:Mr Ace,
the DCs only point to internal DNS servers. No issue there.
What I think it's happenning , and I would like clarification from MS
on this, is the registration is taking place at the same time the DNS
server is in the process of writting the zone to disk. What I'm not
clear on, is whther or not DNS will allow a dynamic request while the
zone is being written. I'd think not, but I can't find ANY document
that addresses this scenario.
InJC said:Mr Ace,
the DCs only point to internal DNS servers. No issue there.
What I think it's happenning , and I would like clarification from MS
on this, is the registration is taking place at the same time the DNS
server is in the process of writting the zone to disk. What I'm not
clear on, is whther or not DNS will allow a dynamic request while the
zone is being written. I'd think not, but I can't find ANY document
that addresses this scenario.
I see, thanks for clarifying some of your configuration.
Since I don't know enough about your whole configuration, here are some
general thoughts on this. Disregard if they don't apply.
What OS?
What Service Pack is on this machine? (Note, there are some issues on SP4,
but need to know some more info if it would be the cause).
Just to confirm JC, your AD DNS domain name is not a single label name?
Where any reg entries altered?
Is the DHCP Client service running on the DC?
Yes, this can also come up due to the zone being AD Integrated and AD has
not quite intialized yet for the zone to be available as the netlogon
service tries to register at boot. But this applies if the DC is pointing to
itself and the only DNS server running is on itself and the zone is AD
Integ. If pointing to another internal DNS server, then as long as that zone
has updates allowed, and it's up and running, and it's not a single label
domain name, adn the zone is spelled correctly (same as the Primary DNS
Suffix on the DC and the same as the domain name in AD), I can't see why you
would get that. So yes, it will allow updates.
Also, if the server it's pointing to is not authorative for the zone or it
can't provide the authorative server for the zone, registration will fail
too.
Here's some articles I have on it. Once again, disregard if some or none of
them apply.
252695 - DNS Server Generates Event 4011 and Event ID 5781:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q252695
257462 - Dynamic Update Does Not Work Using BIND DNS Forwarder [shows Event
ID 5781]: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q257462
259277 - Troubleshooting Netlogon Event 5774, 5775, and 5781:
http://support.microsoft.com/default.aspx?scid=kb;en-us;259277
311354 - Event 5781 Occurs After Domain Controller Changes Domain:
http://support.microsoft.com/?id=311354
244669 - Dcpromo.exe Does Not Create Records in the DNS Zone When Windows
2000 Configures DNS and Event ID 5781:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q244669
--
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
JC said:Ace,
I realized my reverze zone was not dynamic. Changed it to dynamic
earlier today and haven't seen the problem so far.
JC said:Ace,
yes, i enabled dynamic DNS for the reverze zone.