cancel
Showing results for 
Search instead for 
Did you mean: 

Private DNS cannot be accessed?

josewick
Hooked
Posts: 7
Registered: ‎06-09-2010

Private DNS cannot be accessed?

Hi all

 

I have recently made an DNS change on my phone (pixel 6) point to adguard to stop the annoying ads when running some apps. It works great but for some reason, every so often (like once of twice in an hour), it will say "Private DNS cannot be accessed" with no internet access, and it will however restore automatically after a short while (may be a minute of 2)..

Type that into AI and it says i can go into the router setting to turn off the "safeguard", but I cannot always trust the AI these days, in case it compromises the safeguard to my other devices at home using the same network.

Anyone got any info on this please?

Thanks

7 REPLIES 7
PhilipHeyes
Pro
Posts: 267
Thanks: 112
Fixes: 1
Registered: ‎10-11-2021

Re: Private DNS cannot be accessed?

I see the same when using an Android Private DNS, the message comes when the mobile looses its internet connection.

This effect is not limited to Adguard DNS, the same will occur if Cloudflare or Google DNS are configured.

josewick
Hooked
Posts: 7
Registered: ‎06-09-2010

Re: Private DNS cannot be accessed?

Is there a solution to it?
I asked support team and to my surprise, the agent threw me to the forum and said he doesn't know 🤔
Dan_the_Van
Superuser
Superuser
Posts: 4,271
Thanks: 2,562
Fixes: 124
Registered: ‎25-06-2007

Re: Private DNS cannot be accessed?

Gemini AI provides this answer to me

It sounds like you are experiencing a common issue with Android’s Private DNS feature. When your Pixel 6 displays "Private DNS cannot be accessed," it means the phone sent a request to AdGuard’s servers but didn't get a response fast enough, or the connection was momentarily interrupted.

Because Android prioritizes security for Private DNS (DNS-over-TLS), it will "fail closed"—meaning it cuts off internet access entirely if it can't verify the encrypted DNS connection, rather than falling back to an unencrypted (and potentially monitored) DNS.

Why this is happening
There are three likely culprits for these intermittent drops:

Server Latency: AdGuard’s public servers occasionally get overloaded or undergo brief maintenance. If your phone doesn't get a response within a specific timeout window, it triggers the error.

Network Switching: When your Pixel 6 handovers between Wi-Fi and LTE/5G, or between different Wi-Fi access points, the encrypted tunnel can "break" momentarily.

Battery Optimization: Sometimes, Android’s aggressive power management on the Pixel can cause brief hiccups in background network processes.

How to Fix It
1. Try an Alternative AdGuard Endpoint
AdGuard has multiple server addresses. If you are using the default one, try switching to the "Non-filtering" or "Default" alternative to see if a different server cluster is more stable for your region.

Current: dns.adguard.com

Try: dns.adguard-dns.com (This is their newer, globally distributed Anycast address which is often more stable).

2. Reset Network Settings
If you’ve recently updated your Android version, the network stack might have some cached "junk."

Go to Settings > System > Reset options.

Select Reset Wi-Fi, mobile & Bluetooth.

Note: You will have to reconnect to Wi-Fi networks and re-pair Bluetooth devices.

3. Disable "Adaptive Connectivity"
This is a Pixel-specific feature designed to save battery by switching between 5G and 4G, but it is notorious for causing Private DNS drops during the switch.

Go to Settings > Network & internet > Adaptive connectivity.

Toggle it Off.

4. Use the "Automatic" setting as a Test
If the drops continue, change your DNS setting from "Private DNS provider hostname" back to Automatic for a few hours. If the internet still drops, the issue is your ISP or hardware. If the drops stop, the issue is definitely the AdGuard server handshake.

A More Robust Alternative: The AdGuard App
If you find the built-in Android Private DNS setting too "brittle," consider using the AdGuard App (sideloaded from their website) instead of the system setting.

The app creates a local VPN on your phone.

Unlike the system setting, the app can be configured to "fail open," meaning if the ad-blocking server is down, your internet stays on (you'll just see ads for a minute).

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

josewick
Hooked
Posts: 7
Registered: ‎06-09-2010

Re: Private DNS cannot be accessed?

I looked it up on AI and one said I had to turn off something in the Plusnet router, which will compromise the safety amongst other connected devices at home.

I don't get this problem when connecting to other WiFi or most certainly no issue when using data connection. Just when I get home and connect to Plusnet I get that this..
Dan_the_Van
Superuser
Superuser
Posts: 4,271
Thanks: 2,562
Fixes: 124
Registered: ‎25-06-2007

Re: Private DNS cannot be accessed?

Have you enabled 'Safeguard' on your account https://www.plus.net/my-account/safeguard/ ?

It changes the DNS hosts on your account to 213.120.234.38 and 213.120.234.42 which can be confirmed on the hubs

Home >Status page.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

josewick
Hooked
Posts: 7
Registered: ‎06-09-2010

Re: Private DNS cannot be accessed?

This is the bit I mean. I think it's on. But if I have it off , meaning the rest of the devices in the network is not safeguarded 😅
PhilipHeyes
Pro
Posts: 267
Thanks: 112
Fixes: 1
Registered: ‎10-11-2021

Re: Private DNS cannot be accessed?

The Router's DNS settings are bypassed by using Private DNS.

You might try to make your mobile more stable on Wi-Fi ...

Disable "Switch to mobile data"

Settings >> Connections >> Wi-Fi >> ... ( 3 dot menu ) >> "Switch to mobile data"  ( set to OFF )