locked
Reverse DNS IPv6 lookup RRS feed

  • Question

  • Hi All,

     

    DNS is running on Server 2008 SP2.  My workstation is Windows 7.  When I do a forward lookup on a server running windows 2008, I get the IPv4 and IPv6 addresses.  When I do a reverse lookup I only get the IPv4 address.  How can I enable it so I can get the IPv6 address when I do a reverse lookup?

     

    Now, we are not using IPv6 on our network but from the many articles I have read, we also don’t want to disable it.  The addresses are statically assigned as well.

    Tuesday, May 4, 2010 9:19 PM

Answers

All replies

  •    For reverse lookup to work you must have a reverse lookup zone in DNS. It sounds like your DNS have one for IPv4 but not for IPv6.

     


    Bill
    Tuesday, May 4, 2010 11:44 PM
  • Hi,

    Thanks for the post.

    When you create an IPv6 reverse lookup zone using DNS Manager, the New Zone Wizard prompts you for the IPv6 address prefix of the subnet that contains the address range for which the reverse lookup zone is responsible. This address is entered using the normal IPv6 convention, including the length indicator. For example, to specify a 64-bit address prefix for the address range that begins with FE80, you enter FE80::/64. The resulting zone name is constructed by reversing the hexadecimal digits in the expanded address prefix, separating them with periods (that is, creating a logical subdomain name from each digit), and appending the result to the “root” domain name. For example, specifying FE80::/32 in the wizard results in the IPV6 reverse lookup zone name of 0.0.0.0.0.8.e.f.ip6.arpa.

    Hope this helps.

    Miles

    • Proposed as answer by czKKill Saturday, July 24, 2010 10:28 PM
    Wednesday, May 5, 2010 9:09 AM
  • Thanks!

    Hi Miles,

    I am looking at IPv6 Address Prefix wizard.  When I do an nslookup of an address this is the address I get back, 2002:8e19:4f89::8e19:4f89, I would assume that is the standard Microsoft address.  How do I go about entering in this in the wizard?  Man this IPv6 is way different.

    Thanks a bunch.

    Wednesday, May 5, 2010 10:28 PM
  • Hi,

    Thanks for the update.

    I suggest you could first take a look at the following articles:

    DNS Enhancements in Windows Server 2008

    http://technet.microsoft.com/en-us/magazine/2008.01.cableguy.aspx

    Introduction to IPv6

    http://technet.microsoft.com/en-us/library/bb726944.aspx

    Hope this helps.

    Miles

     

    • Marked as answer by toolbox Thursday, May 6, 2010 6:22 PM
    Thursday, May 6, 2010 5:38 AM
  • Thanks Miles,

    It looks really intimidating but not so bad once you start playing around with it.

    Cheers.

    Thursday, May 6, 2010 6:22 PM
  • Hi toolbox,

    Hope you will enjoy our TechNet Forum.

    Thanks,

    Miles

    Friday, May 7, 2010 2:40 AM
  • Hi,

    I was just building a Server 2012R2 Server and got some weird results, run nslookup, get the usual server not found because it wants to use ipv6 instead of ipv4.

    What I did to fix it was run ipconfig, the IPV6 address was fd8c:d76:acd8:cf00:7809:c988:ed82:493c

    I then went to the properties for IPv6 on the network card and made that address a static address, it auto gives it the 64 bit subnet.  This server was a DC so I made the ipv6 dns the same IP.

    I set up a reverse dns ipv6 zone for fd8c::/64 and created a PTR record in that zone by putting in  7809:c988:ed82:493c at the end of the fdc8c address that it starts with by default.  I had to manually give it my server address myserver.mydomain.local and now nslookup and the server in general is happy.

    I had to give the 2nd Server on the virtual server a similar static ipv6 address and then it also works with nslookup.

    Darren

    Friday, February 17, 2017 12:32 PM