Android DOT shows Unconfigured
Hello,
Context :
- DNS setting from DHCP (IPv4 & IPv6) all set to a NextDNS profile
- WAN IP is a fixed one
Everything is working fine on all the device of the network when using DNS port 53.
Same per device setting DoT or DoH manually.
However, I found a problem using a Meta Quest 2 (running Android), test.nextdns.io shows :
status: OK
protocol: DOT
but no profile shown
(different test with IPv4 or IPv6 with same result...)
But on my.nextdns.io :
it says the device is using NextDNS with no configuration.
So no filtering is working, it resolves everything
Unexpected situation...
I have been able to reproduce that on my phone by just setting in the connexion setting to use "Private DNS" automatically (instead of indicating a custom DoT address)
There is no setting on the Meta Quest 2 to set how to connect to the DNS, it uses "Private DNS" automatically by default (so DoT).
Can you please do something to either :
- handle the request coming in DoT on the custom IP addresses set by DHCP for DNS ?
like for port 53
- refuse the request on those IPs, so the device uses port 53 instead ?
Or maybe you might see another solution.
Thanks !
Best,
Olivier
Reply
Content aside
- 2 wk agoLast active
- 54Views
-
1
Following