clarification on KB #300684 (Netlogon with Single-Label DNS issue)
Posted on 2004-04-12
I used EventID.net for finding MS KB#300684 but I have a question on it's implementation.
Q1) the DCLocator Configuration section mentions "set" the AllowSingleLabelDnsDomain (dword) value to 0x1. But I don't have such a dword entry. Should that have read "add or set" like later in the document about the DNS Client Config? - basically, should I add such a value?
Q2) we have only 1 site, a 2000 SP4 DC and a newly promoted 2003 DC. The domain's DNS name was setup as a single label name about 5 years ago when it was a dual NT system (before my time) Do I even need to worry about the DCLocator value since we have no other forests? or should this dword value be set anyways in both DCs and in all 2000/XP clients?
Q3) the "DNS clients" section says that all DCs need to dynamically register DNS records in a single-label DNS zone. I've set the UpdateTopLevelDomainZones (dword) in the 2000 SP4 DC as stated: HKLM\System\CCS\Services\DnsCache\Parameters. But the spot that I'm supposed to use in 2003 for that dword value (HKLM\Software\Policies\Microsoft\Windows NT\[DNSClient]\<here>) is missing DNSClient - should I make a 'new Key' here? and place the DWord value in it?
After making the changes on the 2 DCs, should the errors subside from their system logs? I've got about 80 XP clients that'll need the "UpdateTopLevelDomainZones (dword)" just want to know what to expect, progress-wise, before I figure out a script to update the other registries en-masse.
BTW, all roles moved to the 2k3 box. nslookup reports the proper DNS server (x.x.x.6, the 2k3 box) and sysvol replicates, DNS generally seems to be running smoothly, except for this warning in evenet log (id: 5781)