<div>
Check out this Microsoft forum post.<br />
<br />
&nbsp;<a href="http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/3a1c9334-54ba-4845-b7c0-ef8ce5454276" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/3a1c9334-54ba-4845-b7c0-ef8ce5454276</a>
</div>


<div>
Try this<br />
<br />
<a href="http://social.technet.microsoft.com/Forums/nl/winservergen/thread/0759595a-ee04-409b-9836-427ee54cbf32" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/nl/winservergen/thread/0759595a-ee04-409b-9836-427ee54cbf32</a><br />
<br />

<blockquote>
I suggest we try the following 3 suggestions to troubleshoot this issue.(please check if it worked after using each method)<br />
<br />
1. &nbsp; &nbsp; &nbsp;uninstall IPv6 from the NIC<br />
<br />
To uninstall use the following command<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; netsh interface ipv6 uninstall<br />
<br />
We need reboot after this.<br />
<br />
&nbsp;<br />
<br />
2. &nbsp; &nbsp; &nbsp;Re-register DNS record<br />
<br />
Stop the DNS service.<br />
<br />
Open ” %systemroot%\System32\Conf<wbr />ig “ folder, delete Netlogon.dns file.<br />
<br />
Restart the DNS service.<br />
<br />
run &quot;net stop netlogon&quot; and &quot;net start netlogon&quot; for register again. If necessary, please restart the server.<br />
<br />
&nbsp;<br />
<br />
3. &nbsp; &nbsp; &nbsp;modify register<br />
<br />
HKEY_LOCAL_MACHINE\SOFTWAR<wbr />E\Policies<wbr />\Microsoft<wbr />\Windows NT\DNSClient<br />
<br />
Name: UpdateTopLevelDomainZones<br />
<br />
Data Type: REG_DWORD<br />
<br />
Value: 0x1<br />
<br />
&nbsp;<br />
<br />
IMPORTANT- If the DNSClient key does not exist you must create it using the following method.<br />
<br />
1) &nbsp; &nbsp; &nbsp;Right click on &quot;Windows NT&quot; and select &quot;New Key&quot;<br />
<br />
1) &nbsp; &nbsp; &nbsp;Name the new Key &quot;DNSClient&quot;.<br />
<br />
Once done proceed to add the &quot;UpdateTopLevelDomainZones<wbr />&quot; reg entry with the correlating value of &quot;1&quot;<br />
<br />
&nbsp;<br />
<br />
HKEY_LOCAL_MACHINE\System\<wbr />CurrentCon<wbr />trolSet\Se<wbr />rvices\Net<wbr />logon\Para<wbr />meters<br />
<br />
Name: AllowSingleLabelDnsDomain<br />
<br />
Data Type: REG_DWORD<br />
<br />
Value: 0x1<br />
<br />
&nbsp;<br />
<br />
After that, please try to run netdiag and check if the errors continue. 
</blockquote>
</div>


<div>
I meant to mention that none of the clients are domain members.
</div>


<div>
For btpringle: Actually, my problem is the reverse. &nbsp;I get PTR records but no A records.
</div>


<div>
Is the server configured to allow &quot;unsecure updates&quot;?
</div>


<div>
The server does not permit unsecure updates. &nbsp;However, XP works and Win7 doesn't so I'm not sure how that applies. &nbsp;Also, neither the forward or the reverse zones permit unsecured updates.<br />
<br />
Number-1, I made your changes and booted with no effect. &nbsp;There was no netlogon.dns file. &nbsp;I had to add both keys and values. &nbsp;And, netdiag did find an old artifact of a dns server that had been removed. &nbsp;I corrected that and rebooted again to no effect.<br />
<br />
Thanks...RG
</div>


<div>
One more note, IPv6 would not uninstall. &nbsp;The netsh command doesn't support interface and the GUI doesn't permit uninstall. &nbsp;It is disabled but not uninstalled.
</div>


<div>
From researching this it appears that Vista and higher will only get added if the server supports unsecure updates.
</div>


<div>
Okay, wait a minute. &nbsp;I might have gotten confused on that series of updates Number-1 requested.<br />
<br />
The servers do not have IPv6. &nbsp;It is on Win7. &nbsp;So, I did all the changes on Win7.<br />
<br />
Were some of them supposed to be done on the server?<br />
<br />
Thanks...RG
</div>


<div>
Check the IP settings on the workstation. There is supposed to an option for automatically adding the computer info to dns.
</div>


<div>
Okay, ran all the updates on both servers and rebooted then rebooted win7 with no effect.<br />
<br />
Yes, the IP settings request dns registration in win7 the same as xp.<br />
<br />
Thanks...RG
</div>


<div>
btpringle can you provide a URL regarding your research on unsecure updates above Vista?<br />
<br />
If this is the case, I wonder why the PTR records are getting updated when the A records are not... <br />
<br />
Thanks...RG
</div>


<div>
Allowing unsecure updates did allow the win7 machine to register in dns. &nbsp;I am not happy with this as a solution, of course. &nbsp;Seems like a hole someone could drive a mac truck through.<br />
<br />
If I can find references regarding this, it'd help. &nbsp;Right now, I am leaving this open.<br />
<br />
Thanks...RG
</div>


<div>
Here is an appropriate article. &nbsp;It is lengthy so I'll have to read it in the morning. &nbsp;But, I read enough to know it applies and even explains why there is a difference in PTR records and A records as DHCP registers the PTR records but the client can request DHCP to permit the client to register the A records so the client has ownership. I don't know if it can help explain how to secure updates, but I believe it may. &nbsp;In any case, recognizing that unsecured updates are working certainly narrows the search. &nbsp;Thanks...RG<br />
<br />
<a href="http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/989e0771-1d6f-4711-bfce-f082ce77b5d9/" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/989e0771-1d6f-4711-bfce-f082ce77b5d9/</a>
</div>


<div>
Interesting information. &nbsp;I checked the ownership of the win7 A record and it is SYSTEM. &nbsp;I checked the ownership of an xp A record and it was the computer account. &nbsp;That difference is obviously at issue. &nbsp;The win7 computer account is not listed under security permissions at all. &nbsp;The xp computer account is specifically listed with full control. &nbsp;Haven't solved this.<br />
<br />
Also, that reference suggested resetting dns domain security to default. &nbsp;Mine were very corrupted. &nbsp;Setting it to default cleared that up, but I still need to permit unsecured updates and they are still owned by SYSTEM.<br />
<br />
Until tomorrow. &nbsp;So long and thanks for all the fish...RG
</div>


<div>
<a href="http://www.petri.co.il/forums/showthread.php?t=31307" rel="ugc">http://www.petri.co.il/forums/showthread.php?t=31307</a><br />
<br />
<a href="http://www.winvistatips.com/re-authorizing-non-domain-computer-access-dns-t802665.html" rel="ugc">http://www.winvistatips.com/re-authorizing-non-domain-computer-access-dns-t802665.html</a><br />
<br />
<a href="http://www.techtalkz.com/windows-server-2003/442568-update-2003-dns-non-domain-member-clients.html" rel="ugc">http://www.techtalkz.com/windows-server-2003/442568-update-2003-dns-non-domain-member-clients.html</a><br />
<br />
<a href="http://www.tek-tips.com/viewthread.cfm?qid=1436181" rel="ugc">http://www.tek-tips.com/viewthread.cfm?qid=1436181</a><br />
<br />
<a href="http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/155c3baa-db75-4de5-84e9-24850c5bdb42/" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/155c3baa-db75-4de5-84e9-24850c5bdb42/</a><br />
<br />
<a href="http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/7f4e21d6-cffb-4519-80dd-12cecaa880ff/" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/7f4e21d6-cffb-4519-80dd-12cecaa880ff/</a>
</div>


<div>
Working on this today, I changed a Default Domain Controller GPO. &nbsp;After the change, one of the DC's could no longer edit any GPO using the standard dcpol.msc through Administrator Tools. &nbsp;I spent most of the day correcting that problem, figuring that one of my edits caused the problems which wasn't the case.<br />
<br />
Don't you just hate it when you change something then it breaks only to find out your change had NOTHING at all to do with it?<br />
<br />
Strangely enough, the fix was to ensure that the two NICs had the correct priority where the Public NIC was ahead of the Private NIC which only talks to the other DC...<br />
<br />
<a href="http://edwinfriesen.nl/content/?p=732" rel="ugc">http://edwinfriesen.nl/content/?p=732</a><br />
<br />
Oh, I checked to ensure that this fix didn't actually correct the problem I am chasing. &nbsp;It doesn't...<br />
<br />
On to the real problem. &nbsp;Thanks...RG
</div>


<div>
I do. &nbsp;They share a private network, just between the two of them, to support storage communication.
</div>


<div>
Okay, btpringle, you led me to the resolution of the problem through:<br />
<br />
<a href="http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/155c3baa-db75-4de5-84e9-24850c5bdb42/" rel="ugc nofollow">http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/155c3baa-db75-4de5-84e9-24850c5bdb42/</a><br />
<br />
They key is not to permit nonsecure updates, though. &nbsp;It is to set DHCP up to Always update A and PTR records and make sure it has appropriate credentials to permit those updates.<br />
<br />
I'll give you the points if you respond to this because I don't want to accept your previous answer since it is misleading. &nbsp;Okay? &nbsp;Thanks...RG
</div>


<div>
For non-domain computers, set up DHCP to update both A and PTR records in DNS.
</div>


<div>
Oddly enough, I actually encountered this problem today...<br />
<br />
For anyone who is trying to figure this out in the future, here are the steps.<br />
<br />
1. Open DHCP on the server<br />
2. Expand DHCP | server.domain | IPv4<br />
3. Right-click on IPv4 and select &quot;Properties&quot;.<br />
4. Select the &quot;DNS&quot; tab at the top of the window.<br />
<br />
Make sure that the following are selected:<br />
&nbsp; -- Enable DNS dynamic updates according to the settings below:<br />
&nbsp; &nbsp; &nbsp; -- Alway dynamically update DNS A and PTR records<br />
&nbsp; -- Discard A and PTR records when lease is deleted<br />
&nbsp; -- Dynamically update DNS A and PTR records for DHCP clients that do not request updates. (Only if there are older clients)<br />
<a href="https://filedb.experts-exchange.com/incoming/2012/07_w29/590379/DHCP-IPv4-DNS-Properties.PNG" target="_blank" class="file-inline" title="DHCP IPv4 DNS Properties (23 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>DHCP-IPv4-DNS-Properties.PNG</a>
</div>


DHCP-IPv4-DNS-Properties.PNG

<div>
Yes, but you also have to make sure you have valid credentials in the same dialog as I mentioned. &nbsp;Thanks...RG
</div>


<div>
<div class="content wysiwyg-content">
I have a dual win2k3 dc server configuration running dns and dhcp for my network. &nbsp;Everything seems to be working except that win7 will not register in dns. &nbsp;My xp machines that also use dhcp register just fine. &nbsp;<br />
<br />
I can access servers, shares and printers using win7. &nbsp;I just can't access my win7 machine by name across the network because the dns entry is missing.<br />
<br />
OBTW, the reverse lookup is actually updated! &nbsp;It's only the forward lookup that is missing.<br />
<br />
IPv6 is disabled. &nbsp;The win7 nics are configured to register in dns the same way the xp machines are configured. &nbsp;Issuing start \\servername to the dns server works just fine so credentials are good. &nbsp;Event logs show no issues on either win7 or dns. &nbsp;<br />
<br />
Help? &nbsp;Thanks...RG
</div>
</div>


I have a dual win2k3 dc server configuration running dns and dhcp for my network.  Everything seems to be working except that win7 will not register in dns.  My xp machines that also use dhcp register just fine.  

I can access servers, shares and printers using win7.  I just can't access my win7 machine by name across the network because the dns entry is missing.

OBTW, the reverse lookup is actually updated!  It's only the forward lookup that is missing.

IPv6 is disabled.  The win7 nics are configured to register in dns the same way the xp machines are configured.  Issuing start \\servername to the dns server works just fine so credentials are good.  Event logs show no issues on either win7 or dns.  

Help?  Thanks...RG

win7 won't register in win2k3 dc server dns

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Windows 7 is an operating system from Microsoft. Features include multi-touch support, a redesigned Windows Shell with a new taskbar, referred to as the Superbar, a home networking system called HomeGroup, and performance improvements.

Windows 7

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.