Private DNS on Android-Device #8051
Replies: 3 comments
-
|
Adguard is using Port 53 and not 853 like set up under the Encryption settings.
Could this be the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Some recommendations. Test DoT from outside your network: If this fails, Android’s Private DNS over DoT will fail too. To verify the TLS handshake and hostname: Confirm AdGuard Home is listening on port and the firewall is open Also if you are using Cloudflare proxy. The "orange cloud" doesn't proxy port 853. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the aswer with the hints. I have adguard home runnig on adguard.mydomain.com In the Cloudflare-Dashboard I added a CNAME for I can reach my Adguard-Web-UI, but
give me the following answer: 100.64.0.1 is the Tailnet-IP from the TrueNAS. When I change the A-Record to the Adguard-Tailnet-IP and disable the ngnix-Proxy-Host for adguard.mydomain.com, but than I can't reach my Adguard-UI any more and the privat DNS also not working on my android device. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
I set up Adguard Home, following the guide in the Adguard-Blog:
https://adguard.com/en/blog/adguard-home-on-public-server.html
Adguard is working except one last thing I can't get working.
I wanted to use encrypted DNS natively on my Pixel like this:
But it's not working, I get the message:
Network has no Internet access
The private DNS server cannot be accessed.
The DNS-entry for this is at cloudflare.
Did anybody get this working?
Beta Was this translation helpful? Give feedback.
All reactions