locked
Ipv6 DNS CNAME resolve problem RRS feed

  • Question

  • Hi folks,
    i´m using ipv6 on windows 7 x64 via openvpn and everything works fine except this case:
    ipv6.google.com has only a CNAME to ipv6.l.google.com which has no A entry (since its for ipv6-testing)

    using "ping ipv6.google.com" doesn't work. Host not found.
    using "ping -6 ipv6.google.com" works fine.
    using "ping ipv6.l.google.com" works fine too.

    so there seems to be a bug where the adress isn't resolved correctly
    i have tried this with another example (on my own domains)
    cname.root24.mobi points to v6-only ipv6.root24.mobi
    ipv6.root24.mobi only has AAAA entries

    using "ping cname.root24.mobi" doesn't work
    using "ping -6 cname.root24.mobi" works
    using "ping ipv6.root24.mobi" works too

    the problem is on IE7, tracert, <everything else> the same.
    Seems like this problem only exist in windows 7 (xp 32bit resolves everything correctly, using ping instead of ping6 works even)

    Sunday, February 28, 2010 1:38 PM

All replies

  • I have the same problem

    Is here any solution?

    Tuesday, November 23, 2010 8:13 AM
  • using "ping ipv6.google.com" doesn't work. Host not found.
    using "ping -6 ipv6.google.com" works fine.
    using "ping ipv6.l.google.com" works fine too.

    Hi!

    Up!

    I have the same problem.

    Is here any solution?

    Tuesday, August 14, 2012 8:30 AM
  • Same issue on 2012 R2 latest patches.    If there is a CNAME to a name with only one AAAA record tand no A Recored, this issue arises.   This difficult to get around in the browser, because there is no command to force a browser to use ipv6 like ping -6.
    Thursday, November 5, 2015 12:35 AM
  • Same here on Windows 10 Enterprise, but everything works fine on my Arch Linux box. The only solution I came up with is to set up a local DNS resolver and filter out these CNAME records. Really surprise to see that it is still not fixed.
    Tuesday, November 7, 2017 2:07 AM