NextDNS CLI Client IPv4 Only
Asus Merlin RT-AC86u.
When running the CLI NextDNS client, DNS traffic goes through IPv4 only. When uninstalled this goes through IPv6.
13 replies
-
The CLI uses both but connects to only one at a time. It will switch endpoints every now and then, if your IPv6 endpoint is a lot slower than the others it won’t be chosen very often if at all.
-
Thanks I will set it up and leave it running for a while then and see what happens. So if it is using IPv4 NextDNS it will still resolve and send IPv6 traffic too?
-
Yes the NextDNS IPv4 server you connect to will resolve IPv6 addresses. It will not however send the requests by IPv6, only IPv4 but that should not stop your devices from using an IPv6 connection, it’s only the domain lookups using IPv4.
Hope that explains it enough for you but if not or you have any more questions just ask away. -
Thank you for replying so quickly. That makes sense and good to know that whether a IPv4 or IPv6 connection is used won't effect which may my Internet traffic goes. However my dashboard is now showing 90% of DNS traffic going via the IPv4 address after installing the script and https://cmdns.dev.dns-oarc.net/ reports that transports RPKI IPv4 and IPv6 are no longer working although everything else passed, and other tests that TLS no longer working however I understand the CLI client uses DoH so it's probably fine.
Perhaps it's load balancing then although it is curious how it falls back primarily to IPv4 for DNS resolution - perhaps it's faster for some reason. -
Try visiting https://ping.nextdns.io in a web browser and it should show you the times for both IPv6 and IPv4 NextDNS PoPs to compare.
-
this page is just black for me, and when I first visited, it acted like it was struggling to resolve
-
hmm it eventually loaded something.
After a few refreshes it sometimes loads stuff.. like the most recent:
```
oplink-hou 8 ms (ultralow1)
vultr-dal 12 ms
smarthost-mci 21 ms
anexia-atl 24 ms
zepto-mci 26 ms (anycast1)
vultr-atl 28 ms
host4-phx 30 ms
smarthost-den 30 ms
anexia-den 30 ms
zepto-sjc 40 ms (anycast2)
anexia-dal error
dns2.nextdns.io error (ultralow2
```
-
yeah I can't reach `dns2.nextdns.io` at all
-
I recognize your post was made 10 hours ago, but I'm able to reach `dns2.nextdns.io` right now.
-
thanks... Well IPv6 is not showing as any faster then
From mobile Firefox browser
vultr-syd (IPv6) 78 ms (anycast1)
vultr-syd 79 ms (anycast1)
anexia-bne 80 ms
gsl-syd 86 ms
nautile-nou (IPv6) 94 ms
zetta-bne 99 ms
vultr-mel 102 ms (anycast2)
■ zetta-adl 110 ms (ultralow1)
zappie-akl 110 ms
vultr-mel (IPv6) 111 ms (anycast2)
anexia-bne (IPv6) 114 ms
nautile-nou 122 ms
anexia-per 129 ms
anexia-per (IPv6) 152 ms
gsl-mel 159 ms (ultralow2)
zappie-akl (IPv6) 263 ms
gsl-syd (IPv6) error
dns1.nextdns.io (IPv6) error (ultralow1)
dns2.nextdns.io (IPv6) error (ultralow2)
-
from the NextDNS app (DoubleAngels)
vultr-syd 10 ms (anycast1)
vultr-syd (IPv6) 11 ms (anycast1)
gsl-syd 11 ms
vultr-mel 18 ms (anycast2)
vultr-mel (IPv6) 23 ms (anycast2)
zetta-bne 25 ms
anexia-bne 25 ms
■ zetta-adl 26 ms (ultralow1)
anexia-bne (IPv6) 30 ms
nautile-nou (IPv6) 33 ms
nautile-nou 33 ms
zappie-akl 36 ms
anexia-per 72 ms
anexia-per (IPv6) 77 ms
gsl-mel 199 ms (ultralow2)
zappie-akl (IPv6) 256 ms
gsl-syd (IPv6) error
dns1.nextdns.io (IPv6) error (ultralow1)
dns2.nextdns.io (IPv6) error (ultralow2)
-
Looks like both ultralow IPv6 are having problems with connection. Maybe try running the NextDNS diag if you can.
-
Thanks just ran it and sent some logs in - from a Linux laptop as the router doesn't have mktemp available so it wouldn't run there. Interestingly the diag reports no IPv6 available, although DNS tests report that it is and passes as such. I am not sure why the diag tool would fail on IPv6 while everything else passes.
Not sure if it's related but Netflx was working on the TV but Amazon and Disney were not - removed the CLI client and rebooted the router and TV and is fine now. May just be a coincidence though as I couldn't see anything blocked in the router although I did notice Netflix connecting via IPv6 in the NextDNS log.
-
Content aside
-
1
Likes
- yesterdayLast active
- 13Replies
- 86Views
-
4
Following