What's new is that your NextDNS configuration profile is preserved even if your client can't do IPv6. We did DNS-over-HTTPs previously for the big public DNS providers, but now we also do DoH for NextDNS, using IPv4 or IPv6 for the underlying TCP connection as needed, but always passing through your NextDNS configuration.
The current UI just makes you paste in your NextDNS config-specific IPv6 address as a means of parsing out your config from the lower bits of the address. We have better UI coming.
(We don't do the NextDNS traditional port 53 DNS. They don't really support it with IPv4. There's a IP linking mechanism but it doesn't work with multiple devices)
Yes. The DNS bootstrap phase is annoying and complicated though. Currently we only do DoH for the big public DNS providers that have well known anycast IPs for their DoH endpoints. That means there's no bootstrap needed.
What's new is that your NextDNS configuration profile is preserved even if your client can't do IPv6. We did DNS-over-HTTPs previously for the big public DNS providers, but now we also do DoH for NextDNS, using IPv4 or IPv6 for the underlying TCP connection as needed, but always passing through your NextDNS configuration.
The current UI just makes you paste in your NextDNS config-specific IPv6 address as a means of parsing out your config from the lower bits of the address. We have better UI coming.
(We don't do the NextDNS traditional port 53 DNS. They don't really support it with IPv4. There's a IP linking mechanism but it doesn't work with multiple devices)