0

AAAA only record issue

I own a domain set to have AAAA record only, pointing to my (obviously IPv6) home server.

Every morning I can't reach my server because NextDNS resolves my domain to an unknown IPv4 address.

Please see attached screenshots.

As of my server is static IPv6, I set override in my.nextdns settings. It doesn't work.

5 replies

null
    • Calvin_Hobbes
    • 3 mths ago
    • Reported - view

    Does your authoritative DNS server have the bad A record?   If so, you should probably remove it.    

    • R_P_M
    • 3 mths ago
    • Reported - view

    Also to add, in the last image the IP address you see on the NextDNS logs is the originator IP of the dns request, it’s not the dns response.

    Maybe the failure is because of your device is connected to an IPv4 only network?

      • Matteo_D
      • 3 mths ago
      • Reported - view

       That's right. It is not the DNS-resolved IP. I'm seeing things.

      At the time of the malfunction I am at home, under wifi (IPV4+IPv6 wan address and delegated prefix). Also, That IPv4 does not seem to correspond either to my local network (192.168....) or to my IPv4 on a wan connection (100.65...).

      I need to perform more checks at the right time.

    • Matteo_D
    • 3 mths ago
    • Reported - view

    This morning I experienced the problem again and I was able to investigate further.

    tl;dr It is not a NextDNS problem but rather my device is on an IPv4-only network. I still haven't determined which one.

    My Android 14 device appeared to be connected in WiFi, with regular IPv4 (192.168.10.2) and IPv6 (2a06:a:b::2) visible in the device information page. My device could reach the router at the IPv4 address.
    The router had regular WAN IPv4 (100.65.x.y) and IPv6 (2a06:a:b::1) addresses. The router could correctly resolve the IPv6-only domain. And of course the router could reach the IPv6 server.

    A check on my-ip.io from my Android device, however, returns an IPv4 address in range 82.0.0/24.

    This could be Android's automatic connection feature, which keeps the device 'connected' in WiFi, but uses LTE instead. Unfortunately, this condition not only fools me, but also does not enable the VPN I use on LTE network (for the purpose of having IPv6!).
    In other words, a bug or a misbehavior of Android.

    Curiously, the IPv4s usually assigned by my LTE provider are in the range 193.0.0/8.

      • R_P_M
      • 3 mths ago
      • Reported - view

      How strange. Have you looked up any info about the 82.xxx IP address you found your device on?
      A whois check maybe. 

Login to reply

Content aside

  • 3 mths agoLast active
  • 5Replies
  • 90Views
  • 3 Following