We have a windows 2003 native domain and all the A and PTR records are working fine for the Windows XP machines, but we have a few running Windows 7 and they are not registering a PTR record. I tried disabling IPv6 on the clients by unchecking the options in the network as well as well as the registry edit for "DisabledComponents" but it's still not registering. Anyone having this issue? Any ideas?

From your post, I assume that there are A records for the Windows 7 computers, but no PTR records. Is that correct? In Windows 7, PTR records will not be registered by default. You need to change the setting via Group Policy. Please follow the steps below. 1. Enter gpedit.msc in the Start Search box.2. Navigate the following policy. Computer Configuration\Administrative Template\Network\DNS Client\Register PTR Records 3. You can see that the default status is Not Configured. Please change the setting. 4. From the detail information you will see special options after Enable this policy. If you would like to apply this policy to all Windows 7 computers, please create a new GPO for Windows 7 computers OU and edit the policy. Arthur Xie - MSFT

We are experiencing exactly the same problem on a Server 2008 R2 domain with Windows 7 clients. The Windows XP clients are registering a PTR record correctly, but the Windows 7 clients are not registering any PTR records.I have tried Arthur Xie's suggestion of modifying the Group Policy setting to 'Register PTR Records', but this has no effect.I can make the Windows 7 clients successfully register a PTR record by modifying the Advanced Properties of the TCP/IPv4 settings, specifically by setting the "Use this connection's DNS suffix in DNS registration" checkbox on the DNS tab. Wireshark indicates that without this checked the Windows 7 clients do not even request registration of a PTR record whilst talking to the server.You also do not require this box checked on a Windows XP client to have it register a PTR record, which makes me wonder if this is a bug. If not, can someone breakdown for me why this setting is required on a Windows 7 client to have it register a PTR record? Cheers!

We are experiencing exactly the same problem on a Server 2008 R2 domain with Windows 7 clients. The Windows XP clients are registering a PTR record correctly, but the Windows 7 clients are not registering any PTR records. I have tried Arthur Xie's suggestion of modifying the Group Policy setting to 'Register PTR Records', but this has no effect. I can make the Windows 7 clients successfully register a PTR record by modifying the Advanced Properties of the TCP/IPv4 settings, specifically by setting the "Use this connection's DNS suffix in DNS registration" checkbox on the DNS tab. Wireshark indicates that without this checked the Windows 7 clients do not even request registration of a PTR record whilst talking to the server. You also do not require this box checked on a Windows XP client to have it register a PTR record, which makes me wonder if this is a bug. If not, can someone breakdown for me why this setting is required on a Windows 7 client to have it register a PTR record? Cheers! This is what I ended up using to get it to work.. Computer Configuration (Enabled) hide Policies hide Administrative Templates hide Policy definitions (ADMX files) retrieved from the local machine. Network/DNS Client hide Policy Setting Comment Connection-Specific DNS Suffix Enabled DNS Suffix: xxxxxx.org Policy Setting Comment Primary DNS Suffix Enabled Enter a primary DNS suffix: xxxxxx.org Policy Setting Comment Register DNS records with connection-specific DNS suffix Enabled Register PTR Records Enabled Register PTR records: Register only if A record registration succeeds

The behavior of Client not registering PTR record by default is modified prior to Windows7 (mostly during Vista time) and is the intended behavior. The Dhcp Server is responsible for performing PTR record registration on behalf of client. Incase if dynamic DNS registration is not enabled on Server (because of which Server doesnot do PTR registration), Client can trigger registration,if "Use this connection's DNS suffix in DNS registration" is selected in adapter properties. Ravi Kumar - MSFT