Vistadoes not seem to register (PTR) records in DNS reverse zones. It does register (A) records fine. I am not using a Windows DHCP server to register records on behalf of the client, so I am relying on the Windows clientsthemselves to create these records in DNS. All other versions of Windows works fine, including Windows Server 2008. I found this older post that someone stated that MS was suppose to fix this in SP1. I built a computer from a clean Vista w/SP1 installation, and PTR records are still not being created. When Ienable "use this connection's DNS suffix in DNS registration", as stated in the workaround,the PTR record gets created. Is MS going to fix this? http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1959664&SiteID=17

Hi, Based on my research, the issue that the RTP record of Windows Vista machines cannot be registered in Reverse Lookup Zones has been fixed in SP1. Also, this issue will not occur when Windows Vista is configured to use a static IP address. I would like to confirm what product is being used as the DNS server. What error message is logged in Windows Vista after typing the command ipconfig /registerdns? In addition, please export the Windows IP Configuration by using the command ipconfig /all on the Windows Vista machine and paste to here.

We have a really convoluted infrastructure when it comes to DNS and DHCP. I am starting to think that it may be related to the Vista computers not registering PTR records, but for some reason XP does. I will try to explain what I got going on the best I can. Our Windows clients obtain addresses via DHCP running onNetWare servers. These NetWare servers also have DNS zones that I will refer to as pc.yyyy.com. I do not administrate these servers, but work with the guy who does. DHCP optionsare configured to set a Connection-specific zone suffix of pc.yyyy.com on the client. It also sets the client DNS servers to point to the Active Directory DNS server, running on domain controllers. I will call this zone corp.xxxx.com. The zone is Active Directory-integrated and only allows secure updates. It receives these updates directly from the client and has worked fine for years. The NetWare servers have reverse zones for the DHCP-assigned networks. Computers on the networkcan only resolve reverse lookupsof Windows clientsfrom the NetWare servers. The queries are forwarded up to these servers because I configured the AD DNS with Forwarders. Last week, in order to begin preparing for a migration of DHCP to Windows (which I cannot say how long it will be), I created reverse zones on the Windows DNS servers for theWindows client networks. The XP clients successfully began registering (PTR) records in these zones. The Vista SP1 computers did not. The Vista clients do successfully register (A) records however. No errors are returned when I run ipconfig /registerdns. I have not tried a static IP Vista client yet, but Ican doso when I get back to the office. One thing that does work for the DHCP Vista clients is when I enable "Use connection's DNS suffix in DNS registration". With that checked, it successfully creates a (PTR) in the Windows reverse zone. I do not have this enabled on the XP computers. Now, going back to the NetWare DHCP options, the connection specific suffix being assigned is pc.yyyy.com. This suffix is not being appended to the host record registered in the Windows DNS servers, which is good. However, I am starting to wonder if the Vista is not registering a (PRT) because client is configured with this suffix. It will be difficult for me to confirm that without building out a separate DHCP server in a test environment. Also, why is it that XP, also configured with pc.yyyy.com connection suffix, does register (PTR) records in Windows DNS. If this could be the cause, I can maybe get the DHCP migration projectelevated in priority so that we can decommission the NetWare DHCP and DNS servers. I would have to get the issueconfirmed though. Iwish to avoid setting the "Use connection's DNS suffix in DNS registration" on all of the Vista computers or using static (PTR) records for these hosts. I will work with the NetWare administrator to see if we can test out some things. Possibly remove the connection-specific suffix in the DHCP options to see if that resolves it. Let me know if you have any thoughts on the situation. Thanks!

I had the NetWare admin remove the connection suffix pc.yyyy.com from DHCP. When I renewed the IP on the client, it no longer included that suffix. However, Vista still does not register a (PTR) record unless I check the "Use connection's DNS suffix in DNS registration" option . I verified that a static IP address client does successfully register the (PTR). What is the difference to Vista?

I set up a test lab with a Windows Server 2008 DC/DNS/DHCP server and a Vista client that was upgraded to SP1. It still does not register a (PTR) record. Thisbug still exists in Vista SP1. I say bug, because the problem does not occur in XP. Iconfigured the DHCP server both with and without a DNS Domain Name suffix option(I believe it is option 15) and that had no effect.When I enabled the "Use connection's DNS suffix in DNS registration" option, theclient successfully register a (PTR).It also register a (PTR) when I configured the client with a static address.

My environment:- 400 Vista SP1 workstations with latest MS update patches (just not SP2)- Non windows DHCP server- Windows 2003 Active Directory with DNS serverNone of the Vista PCs using dynamic IP Addresses have PTRs in their respective Reverse Lookup Zones in our DNS.The handfull of remaining Windows XP machines do have PTRs. Also Vista PCs with static IP address or the ones with the "Use Connection's DNS suffix in DNS registration" checked do create correct PTRs.What is the status of this issue?

Well, upgraded to SP2 and the issue persists, Vista SP2 does not register IPV4 PTRs either.Workaround to get it working is as follows:Create and apply GPO with following settings:- provide connection specific DNS suffix- provide primary DNS suffix- register DNS records with connection-specific DNS suffic- register PTR recordsall under Computer Configuration > admin templates > network > dns clientStrangethat this hasn't been addressed yet - seems easy enough to reproduce.

This behaviour would appear to be by design. See http://technet.microsoft.com/en-us/library/bb727035.aspxunder the section "DNS registration behaviour."Vista is designed to register A, PTR (IPv4) and AAAA records only. This is the same with Windows Server behavior. The only way I have seen IPv6 PTR records go into DNS is when you enter a static IPv6 address and tick the "Create PTR record."So, not a bug, but by design. A good question now would be "Why was it designed this way?"Anthony Sheehy - .net

I was referring to IPv4. The technet article you sent specifically states that IPv4 PTRs should also be dynamically registered. This however does not happen automatically as I said in my previous post. This shows that lack of IPv4 dynamic PTR registration in Vista SP1/SP2 is definitely a bug.