@Marvin_S Hi,

Sure! Thanks for letting me know and that's of course your choice.

Could you explain a bit what exactly is not supported in the setup of nextdns?

  @Marvin_S 

that's too bad because NextDNS is pretty rad!

I was so happy to see these features appear but they are useless in this form

Please try and help

Here's how NextDNS expects the identification:

DNS-over-TLS/QUIC:
Prepend the name to the provided domain (the name should only contain a-z, A-Z, 0-9 and -). Use -- for spaces.
For "John Router", you would use John--Router-abc123.dns.nextdns.io as your DNS-over-TLS endpoint.

DNS-over-HTTPS:
Append the name to the provided URL (the name should be URL encoded).
For "John's Firefox", you would use https://dns.nextdns.io/abc123/John's%20Firefox as your DNS-over-HTTPS endpoint.

Also only the 'default' 'DNS mode' works the 'secure' one doesn't.

Thanks

Thanks Marvin It would be a great opportunity to show TP-Link is also an up to date player in the router business.

Is there a way to get signed up to a beta update channel for the X50 v1?