You are reading a single comment by @aggi and its replies. Click here to read the full conversation.
  • Hey @Velocio maybe you could offer some wisdom for setting up nextdns.io. I had it working on Android by changing the Private DNS hostname option but this morning I'm just getting the error "Private DNS server cannot be accessed".

    My Android: Settings > Network and Internet > Private DNS is set to Android-12345a.dns.nextdns.io where 12345a is your account identifier, and Android- is a prefix that means all logs and analytics in NextDNS will identify that the DNS request came from Android.

    That's it... and it works.

    When doesn't it work? Or... when does it say "Private DNS server cannot be accessed"?

    Occasionally this happens, typically it's either a very poor signal somewhere and in effect the internet cannot be access but it's these initial DNS calls that timeout so it misreports the root cause.

    Or it's a captive hotspot, a public WiFi, with a very restrictive firewall configuration. And until you have got past their login screen the firewall is preventing all other connections. So again... root cause it misreported - if I must use this hotspot I disable the private DNS momentarily, login, and then re-enable.

  • if I must use this hotspot I disable the private DNS momentarily, login, and then re-enable

    Talking about this, I have a feeling that some public hotspots (the tube is the main one I can bring to mind) disable nextdns and VPNs completely. Is this a thing or am I imagining it?

About

Avatar for aggi @aggi started