IPv6 Dynamic DNS Registration


  • Hi Everyone, Recently I've began experimenting with IPv6 in my lab environment and I've ran into an issue.

    Windows Server 2008R2 and Server 2012RTM will not dynamically register reverse IPv6 addresses in DNS. However the IPv4 and IPv6 forward records register as well as the IPv4 reverse record. Just not the IPv6 reverse record.

    The reverse zone is definitely named correctly as toggling the "Update Associated pointer (PTR) record)" check box successfully creates the IPv6 reverse record when apply is clicked. 

    I've ran a packet capture while running an "ipconfig /registerdns" and I can see update queries go out for the 3 other records, but not the IPv6 reverse record. Which leads me to believe this a client side problem rather than server side. 

    Am I missing something here and this is by design or have I come across a bug/not yet implemented feature.

    Thursday, September 06, 2012 12:25 PM

All replies

  • Are you able to manually create the PTR record and successfully perform a lookup?  This should test that the zone setup 'should' be working...
    Tuesday, September 25, 2012 2:53 PM
  • If i manually create the PTR record it resolves fine so i don't think the problem is on the DNS server side.
    Tuesday, September 25, 2012 10:03 PM
  • Hi Dean, just to let you know that I´m experiencing the exact same behavior on a domain controller with Windows Server 2012, so maybe you are right and the problem is with the client.
    Wednesday, October 10, 2012 4:09 PM
  • Hi Dean

    I was just wondering have you checked the radio button for: "Always dynamically update DNS AAAA and PTR records" in the DHCPv6 properties?

    Wednesday, November 14, 2012 9:02 PM
  • We are also having this issue with Server 2012. Even with static set IPv6 addresses, the PTR records are not updated for ipv6 when ipconfig /registerdns is run.

    The ipv4 PTR records are however updated. 

    Monday, November 26, 2012 11:53 PM
  • Not registering IPv6 PTR records is by design.  Not sure why Microsoft decided this, they just did.
    • Proposed as answer by John Adkison Saturday, November 02, 2013 8:18 PM
    Saturday, November 02, 2013 8:17 PM