0

dns.nextdns.io missing IPv6 records

I doubt it is a mistake, but why are there no IPv6 (AAAA) records for this very important endpoint?

11 replies

null
    • Calvin_Hobbes
    • 3 mths ago
    • Reported - view
    > dns.nextdns.io
Server:        127.0.0.1
Address:    127.0.0.1#53  Non-authoritative answer:
Name:    dns.nextdns.io
Address: 209.209.57.165
Name:    dns.nextdns.io
Address: 104.238.181.28
Name:    dns.nextdns.io
Address: 2a0e:6901:410:25:5054:ff:fe1c:7c81
Name:    dns.nextdns.io
Address: 2001:19f0:ac01:170:5400:2ff:fec8:72c8
    • xyzulu
    • 3 mths ago
    • Reported - view

    mmm now that is interesting.. 

    Using my local DNS resolves (Nextdns upstream) as well as others like 1.1.1.1 don't give me any AAAA records.

    Edit: making some progress.. on a Mac with a Nextdns profile installed (but configured to not use the profile on the wifi network) the IPv6 records are just not returned.. on another device, Ubuntu etc without a profile I'm seeing the same as you (other network). Thanks for the solid evidence.. I will keep working on it.

    It may well be a unifi issue as I just started to use their DNS Shield with sdns from Nextdns. It's doing something to queries over IPv6 for sure. On Ubuntu on the unifi network no AAAA records either.. 

      • Calvin_Hobbes
      • 3 mths ago
      • Reported - view

       I am also on a Mac using a profile.   I originally had the same issue you are seeing.   I don't recall how I got both A and AAAA to appear.   You can use the following command within nslookup to get the AAAA answer, but I don't remember how I was able to get both

      set q=AAAA
      • xyzulu
      • 3 mths ago
      • Reported - view

       interesting..

      Using the nextdns-cli connections are made over IPv6 just fine, despite the dns.nextdns.io records being "missing" for me. I'm wondering if this is something deliberate from Nextdns once you have/are using them for DNS resolutions??

      Everything works just fine.. but I'm also the kind of person who looks for answers. Back in the day it was easy to contact Oliver.. now, a bit harder ;)

      • Calvin_Hobbes
      • 3 mths ago
      • Reported - view

       I'm a bit baffled now too.    I have serveral terminal tabs open.   One of them only returns A records.  The others return both A and AAAA records like I pasted in a previous reply to you.

      I don't know why they are behaving differently.   I do know the terminal session that's only giving A records has been open for several days and I've done a bunch of different things with it.  It's possible I somehow set an envenroment variable that's causing problems, but I don't recall doing that. 

      Try opening a fresh terminal and retrying nslookup.

      Many *nix people will say to use dig rather than nslookup.    I've been using nslookup for years and prefer it.   I started on Windows in the 90s and it didn't have dig, it only had nslookup, so that's what I know and use.   Dig is probably good for scripting, but nslookup does everything I need.    I recall reading that nslookup was deprecated, but then it was brought back.

      • xyzulu
      • 3 mths ago
      • Reported - view

       I'm using dig and nslookup (and the MacOS native dns as well).. also using a Mac and Ubuntu server as well as a Debian box on the same network.. all are not returning AAAA records.

      • Calvin_Hobbes
      • 3 mths ago
      • Reported - view

        Perhaps IPv6 is not returned if you don't have a public IPv6 address?   I am not sure because  my connection has both IPv4 and IPv6.

      • xyzulu
      • 3 mths ago
      • Reported - view

      I have both.. I'm certain of that. I can resolve any other IPv6 address.. ie google.com just fine.

      • Calvin_Hobbes
      • 3 mths ago
      • Reported - view

       My previous post was incorrect.  I do not have a public IPv6 address right now.   I might have in the past.   Have you tried completely closing your terminal and trying nslookup again.   My new terminal sessions show both A and AAAA records.

      • xyzulu
      • 3 mths ago
      • Reported - view

       I have.. I have even tried on 2 other linux machines on my network. All have IPv6 and IPv4 however. I could disable IPv6 and then try again.. but I'm not sure if I should bother trying to work out the why on this ;)

      • Calvin_Hobbes
      • 3 mths ago
      • Reported - view

       well, it’s strange.   I hope you get it resolved (haha)

Login to reply

Content aside

  • 3 mths agoLast active
  • 11Replies
  • 92Views
  • 2 Following