Vista not creating PTR record in Server 2003 domain

I couldn't believe your post until I checked it myself .. you're right.
After looking at a client I have a theory: IPv6
By default, IPv6 is enabled. DNS tries to register a RR with an IPv6 address and fails, therefore does not try to register a RR for IPv4.

This is what I get on the client after ipconfig /registerdns

The system failed to register pointer (PTR) resource records (RRs) for network adapter
with settings:

   Adapter Name : {445C639F-0F50-4D1A-9C0D-6ED22A90220A}
   Host Name : BTV0C004
   Adapter-specific Domain Suffix : domain.com
   DNS server list :
           192.168.10.10, 192.168.10.11
   Sent update to server : <?>
   IP Address : 2002:ac6c:a28d::ac6c:a28d

 The cause was DNS server failure. This may because the reverse lookup zone is busy or missing on the DNS server that your computer needs to update. In most cases, this is a minor problem because it does not affect normal (forward) name resolution.

 If reverse (address-to-name) resolution is required for your computer, you can manually retry DNS registration of the network adapter and its settings by typing  "ipconfig /registerdns" at the command prompt. If problems still  persist, contact your DNS server or network systems administrator.  For specific error code information, see the record data below.

mpfister:

Yes, that was my guess as well.  I'll try uninstalling the IPv6 protocol suite from one of my Vista boxes and see if that makes a difference.  I'll let you know if it works after that.

Interesting, I'll give that the work around a try first.  I'm betting your assumption is correct and it's IPv6 that is causing the issue.  I'll let you know the results in a few minutes.

Adding IPv6 reverse lookup zone does NOT help. Event 11157 on Vista client is gone, but no entry for IPv4 reverse lookup.

I tried disabling IPv6 as well as making the registry entry they suggested, the PTR record is still not being created.  Perhaps we've found a new bug mpfister!  =)

I just got a reverse pointer entry in DNS a short time after a reboot (was busy with something different so didn't really measure the time).
So the bug seems to be the reverse pointer not being created when doing ipconfig /registerdns

Did you get the update after creating the IPv6 zone or by disabling IPv6 creating the registry entry fix?

Thanks for all your help on this!

I created the IPv6 reverse lookup zone in DNS, issued an ipconfig /registerdns on the client but had no success creating the reverse IPv4 pointer.
After that I rebooted the same client and suddenly got a reverse IPv4 pointer

I did not disable IPv6

Seems like the workable solution to what Microsoft has setup so far.

mpfister:

Since my IPv6 knowledge is pretty minimal, I was hoping you could help me when creating the IPv6 reverse lookup zone.  The IPv6 address on one of the Vista machines is fe80::782e:238e:10a9:7857%8.  I've had some difficulty locating an article to explain the "%" character and the usage with shorthand IPv6 addresses.

I would guess this IP would be  fe80:0000:782e:238e:10a9:7857:0000:0000.  How would I go about getting the IPv6 reverse lookup zone info out of that and could you explain your method.  

I'll gladly create another post if you'd prefer to answer this for some additional points.

Thanks!

I assume your reverse IPv6 domain zone would be

7.5.8.7.9.a.0.1.e.8.3.2.e.2.8.7.0.0.0.0.0.8.e.f.ip6.arpa

Hope it works.