3

"Private DNS" on Android and pfSense DNS setup conflict?

Hello,

I use NextDNS's DNS, both on the "Private DNS" setting on my Android phone, and on the DNS Resolver custom option of my pfSense router.

It worked for months together (I use my NextDNS phone config , both on 4G and when I'm connected to my router.).

But since a few hours today, without any configuration modifications,  my phone tell me no internet connection when I'm connected to the router.

It work great on another wifi (without NextDNS setting), or on my wifi (with nextDNS Settings) but only if I disabled the "Private DNS" setting.

I don't know why...

Is there a conflict when we use both NextDNS setting on router AND on phone together?

Thank you,

45 replies

null
    • eBKv6q
    • 3 yrs ago
    • Reported - view

    Olivier Poitrey following up on this. I last posted on Dec 23rd. A few days later the issue went away with no configuration changes on my end. I assumed something was adjusted in NextDNS. As of approximately 12 hours ago the "Private DNS cannot be accessed" message is back for android devices.

    Thanks

      • olivier
      • 3 yrs ago
      • Reported - view

      eBKv6q do you have cname flattening enabled in the settings tab?

      • eBKv6q
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey the CNAME Flattening setting is disabled. Thanks

      • olivier
      • 3 yrs ago
      • Reported - view

      eBKv6q was it disabled, or disabling it fixed the issue?

      • eBKv6q
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey Sorry, to clarify the CNAME Flattening setting is and always was disabled for my account. The problem is still occurring.

      • olivier
      • 3 yrs ago
      • Reported - view

      eBKv6q do you have dnssec validation setup on your router? Does it fix if you disable (I know you tried in the past, but this is a different issue).

      • eBKv6q
      • 3 yrs ago
      • Reported - view

      Olivier Poitrey I still have dnssec disabled on the router. Its been off since my initial post on Dec 23rd.

      • Turquoise_Mountain
      • 2 yrs ago
      • Reported - view

      eBKv6q If your using Pfsense then it's probably Pfsense and not NextDNS. Your android devices are not being allowed to reach the surface. It stays within the local network. Adjustments would need to be made to allow your devices to get through Pfsense or it will be automatically blocked.

    • eBKv6q
    • 3 yrs ago
    • Reported - view

    Any updates on this issue? I've experienced the same "Private server cannot be accessed" on android devices for the last 2 weeks.

    Thanks

    • wTm5PK
    • 3 yrs ago
    • Reported - view

    I have been experiencing the same "Private server cannot be accessed" error, with no changes having been made on my network.  I am on Verizon FiOS and using the G1100 router. 

    I am not aware of any way to enable dnssec on the router.  Also, I have CNAME flattening disabled.

    Any other suggestions on resolving this?

      • romain
      • 3 yrs ago
      • Reported - view

      wTm5PK Can you try:

      1. Using "dns.nextdns.io"

      2. Using "anycast.dns.nextdns.io"

      And for which one(s) you're getting the issue?

      • eBKv6q
      • 3 yrs ago
      • Reported - view

      Romain Cointepas can you clarify what we should be trying? Should we visit the two URLs in our browser, or try swapping Android Private DNS to the format device-ID.anycast.dns.nextdns.io rather than the normal device-ID.dns.nextdns.io ?

      Thanks

      • wTm5PK
      • 3 yrs ago
      • Reported - view

      Romain Cointepas anycast.dns.nextdns.io fails to connect consistently, but I have never used that prior to the test you suggested.

      I was originally using dns.nextdns.io when receiving the error. It appears to be working now, but I was sometimes able to get it to work by manually switching from dns.nextdns.io to hardcoding dns2.nextdns.io.

      • Turquoise_Mountain
      • 2 yrs ago
      • Reported - view

      eBKv6q They are connections made to the URLs. Just testing to see if a valid connection can be established. If not, well then there's a problem.

    • Marcos
    • 3 yrs ago
    • Reported - view

    El mismo problema, conectado a red wifi no conecta el dns privado y tampoco tengo acceso a la red.

    • eBKv6q
    • 3 yrs ago
    • Reported - view

    Hello,

    Is there any update on this or additional information we can provide to troubleshoot?

    Thanks

    • fwehrle
    • 2 yrs ago
    • Reported - view

    Hi guys,

    Since a few days, witout any settings changes, this troubles append again.

    I double check my router's and nextdns settings :  dnssec option is disabled, and cname flat too.

    Any changes in your side?

    What can i test/do to solve my problem?

    Thank you very much, and have a nice day

    • fwehrle
    • 2 yrs ago
    • Reported - view

    Thank you.

    I don't know if it apply, since I don't know how to check the CA on pfSense.

    I ask for it on the other post. Wait and see..

Content aside

  • 3 Likes
  • 2 yrs agoLast active
  • 45Replies
  • 2077Views
  • 9 Following