0

Re-link IP address to v6 (or link multiple)

Hi,

New to NextDNS, this has probably been asked and answered many time so apologies -- please forgive the newbie...

I set up my first profile and had no issue linking my IPv4 address.

Since then I now have a v6 address from my ISP and a /48 PD I can use. My router is set up now with the IPv6 addresses of NextDNS -- BUT for the life of me I cannot make the profile link to my v6 even though I've verified (using Curl) that next DNS can see me using the v6 address. I've also tried setting up a new profile and linking that but same issue, still the v4 shows.

I can't tell whether the v6 has linked but the UI can only show one (and chooses the first), or whether for whatever reason my browser / Mac are insisting on sending v4 all the way to the DNS.

I am new to everything -- new to my router / networking environment (Unifi), new to NextDNS, new to IPv6... steep learning curve. If anyone can point me in the right direction, I'd appreciate it. 

Thanks

Alastair

2 replies

null
    • R_P_M
    • yesterday
    • Reported - view

    Ah, right. OK, the IPv6 NextDNS addresses do not require linking, they are unique to your configuration profile. IPv4, on the other hand, does require to be linked (is not unique so needs an identifier).

    • Alastair_MacLeod
    • 6 hrs ago
    • Reported - view

    @r_p_m thanks for the reply but something certainly still is not right.

    I have verified that NextDNS can "see" my IPv6 (using Curl from the terminal / command line). However when I use a browser to make a basic query to NextDNS (calling up my status page) it states clearly that my machine is not using a linked NextDNS profile. Whenever I do link it, my IPv4 pops back up again.

    I have a feeling that what's going on is this:

    - Everything is correctly set on my actual test machine for IPv6 (I've check that it has an IPv6 address on the subnet from my /48 PD that my ISP gave me.

    - On the machine itself I've removed all IPv4 DNS server addresses (so my Mac only knows about IPv6 DNS resolvers, it does of course however still know the IPv4 address of the default gateway).

    - When I bring up my NextDNS status page and re-link it, it links correctly to my IPv4 WAN address (a non-static address assigned by my ISP that periodically rotates). No sign of the IPv6 on the "Linked IP" page).

    I've been at this for a few days now and my guess is this. I have left IPv4 enabled on my router (dual-stacked with IPv6) because not every device, and not every remote host, can cope with IPv6 and I've read plenty of examples where people said that by removing IPv4 completely from the external face of their network they had problems.

    What I think is happening therefore is that my router is defaulting to using IPv4 for outreach, when it should be defaulting to the "superior" IPv6 if a) it is configured - it is, and b) if it works when it reaches out - which it does but only if I force it by using Unix commands like Dig and Curl to tell it exactly what I want or where I want to go.

    Any other ideas welcome!

Login to reply

Content aside

  • 6 hrs agoLast active
  • 2Replies
  • 29Views
  • 2 Following