The phone says the Private DNS server cannot be accessed, or it shows as connected while pages do not open, and a DNS server name is entered in the network settings. That is Android’s strict Private DNS mode: it could not reach the server you chose and, in this mode, does not fall back to ordinary queries. Below: the three modes, four causes, a one-minute check and what we know about this mode together with a VPN.
In short. Open Settings → Network & internet → Private DNS (per Google’s help; your skin may differ), choose Automatic and tap Save, then reconnect the VPN. If pages open, the cause was the hostname mode: the server name, a network that does not pass encrypted DNS, or a server that cannot be reached from the tunnel. Put your own name back as the provider publishes it, and test with the VPN on.
We make Mayak. A VPN app for Android; we do not name or rate other DNS servers or services. 3 free days, no card needed.
🍎 On iPhone Mayak works with the subscription link from your account. INCY was removed from the Russian App Store on 27 October 2026: if you already have it, it keeps working — do not delete it, it cannot be downloaded again from the Russian store right now. With a Russian Apple account, Clash Mi and Shadowrocket are available now (we have not verified them live with our link); Happ and INCY need an Apple account of another country.
The three Private DNS modes
“Private DNS” in Android encrypts only the lookups that turn a site name into an address. Google’s Pixel help lists three options: Off, Automatic and Private DNS provider hostname. Per that help, by default the phone uses Private DNS on every network that can, and Google recommends keeping it on. It also says Private DNS secures only DNS questions and answers and “can’t protect anything else”.
| Mode | What the phone does | If the server does not answer |
|---|---|---|
| Off | Asks the network’s DNS servers, without encryption | No Private DNS error: it is not used |
| Automatic | Tries to encrypt queries to the network’s DNS server; if the server cannot, it works as usual | Falls back to an ordinary query: pages open |
| Provider hostname | Asks only the server you named, and only over an encrypted channel | Does not fall back: names do not resolve and the “cannot be accessed” error appears |
The description of the modes comes from the Android source (where they are called off, opportunistic and provider hostname) and from RFC 8310: the third mode matches the “Strict Privacy” profile, where the client requires an encrypted and authenticated connection, a “hard failure occurs if this is not available”, and it must not fall back to the opportunistic profile during a query (sections 5 and 5.1). That is why only the third mode produces the error.
Why the server is “not accessible”: four causes
- The name is wrong, or the server does not answer over encrypted DNS. The field takes a name, not a numeric address: the server is authenticated by name (RFC 8310, section 6). An extra dot, “https://” at the start, a slash at the end — and the check fails. Take the name from the DNS provider’s own site, not from someone’s comment.
- The network does not pass the port. DNS over TLS uses TCP port 853 by default (RFC 7858, section 3.1). Work, school and hotel networks sometimes pass only the web; then the server is unreachable from that network and works in the next one.
- A Wi-Fi sign-in page. Until you accept the terms, the network does not answer like a normal one, and per DNS providers’ descriptions an encrypted query often fails before sign-in. Sign in with the mode set to Automatic and go back to your own server afterwards.
- A VPN. In 2019 Android started checking strict-mode Private DNS on VPN networks too: the change description says a VPN used to be considered validated at once, skipping the Private DNS hostname resolution, and now the system performs it on VPNs as well (change by Lorenzo Colitti, bug 122652057). The consequence we draw from it: the server you named must answer from inside the tunnel. If the tunnel or its exit does not pass encrypted DNS to that server, the error appears even though everything worked without the VPN.
A one-minute check
- Open the setting. Per Google’s help: Settings → Network & internet → Private DNS. If the item is not there, search the settings for “Private DNS”; other skins (Samsung, Xiaomi, Huawei) use a different path and we do not make one up.
- Choose Automatic and tap Save. Open a few sites. If they open, the cause is the third mode, not the network as a whole.
- If you need your own server (an ad filter, a family DNS), type the name exactly as the provider publishes it: no “https://”, no slash, no port, no numeric address.
- Try another network: switch from Wi-Fi to mobile data or back. Works in one — the cause is the network, not the name.
- Turn the VPN on and test with your own server. If it works without the VPN but not with it, go back to Automatic: you found the fourth cause.
Check it yourself. It is easier to test strict mode and a VPN together once than to guess: within the 3 free days, connect with your Private DNS and without it.
What happens next.
- Create an account in the dashboard: email and password, no card.
- Install the app: from Google Play or as a file from our site. On the first connection Android shows a connection request window: that is how it should be.
- Press one button and open a few sites with your Private DNS mode; if pages do not open, choose Automatic and repeat.
🍎 On iPhone Mayak works with the subscription link from your account. INCY was removed from the Russian App Store on 27 October 2026: if you already have it, it keeps working — do not delete it, it cannot be downloaded again from the Russian store right now. With a Russian Apple account, Clash Mi and Shadowrocket are available now (we have not verified them live with our link); Happ and INCY need an Apple account of another country.
VPN and Private DNS: what we know about Mayak
- Our emulator measurement, 7 November 2026. App version 1.0.25, an Android 36 emulator on its cellular network, five connection modes (AmneziaWG direct and cascaded, X-ray), two of them with Private DNS in hostname mode set to
dns.google. In all five, once the tunnel was up, not one DNS query left outside the tunnel. In the twodns.googlemodes the system’s service output showed Android validated Private DNS on the tunnel network itself: server namedns.googleand validated addresses 8.8.8.8 and 8.8.4.4. So on the emulator the strict mode with that name worked while Mayak was connected. - What that measurement did not cover. A real phone, Wi-Fi, other names, a name that cannot be reached (the error case in this article), the browser’s own “secure DNS”. Each mode was one run of about a minute.
- What the app’s reports show. Of 7,123 diagnostic reports from 15 October to 14 November 2026, strict Private DNS is recorded in 111 and Automatic in 224. The verdicts in those reports do not differ from the rest; the sample is small, and the reports are what people tapped or what the app sent by itself, not a random sample of users. Separately: in the 30 days before 13 November, strict mode was set for 20 of about 800 people who had sent diagnostics.
- The ad and tracker filter. In Mayak it is switched on in Settings → Network (how, and what it removes). By the description of the hostname mode, the phone asks the server you chose, so with that mode the Mayak filter most likely takes no part in name resolution. That is an inference from the description; we have not tested it on a phone.
What we do not promise
- That on your model and skin the item is named and placed as in Google’s help for Pixel.
- That any DNS server will work from our tunnel or from any other network: we checked one name in one environment.
- That a particular app or site will open after you change the mode: the switch only changes whom the phone asks for addresses.
What we checked
- Google’s Pixel help on Private DNS (three modes, the path in Settings, “secures only DNS questions and answers”) — 21 November 2026.
- RFC 8310 (Strict and Opportunistic Privacy profiles, sections 5, 5.1, 6) and RFC 7858 (port 853 by default, section 3.1) — 21 November 2026.
- The Android source change description “Support strict mode private DNS on VPNs that provide Internet” (Lorenzo Colitti, 2019) — 21 November 2026.
- Our own measurement of 7 November 2026 on an emulator (app 1.0.25, five modes) and our own analysis of diagnostic reports from 15 October to 14 November 2026.
What we do not know
- How strict mode behaves with Mayak on real phones and on mobile networks: our own measurement was on an emulator.
- What the items are called and where they are in Samsung, Xiaomi, Huawei and other skins.
- What share of “connected but pages do not open” cases is down to strict mode: the reports do not separate it from other causes.
- The legal side: this article is about how a setting works; we give no legal assessment.
Short answers
What does “Private DNS server cannot be accessed” mean? In the Private DNS provider hostname mode the phone could not set up an encrypted, authenticated connection to the server you named, and it does not fall back to an ordinary query, so site names do not resolve.
What to do first? Choose Automatic and save. If that works, the cause is the server name, the network, or the server being unreachable from the tunnel.
Is Automatic risky? Google recommends keeping Private DNS on, and Automatic is the default. It encrypts queries where the server can; it protects nothing else.
Do I need to turn the VPN off for Private DNS? Not necessarily: try both together. If pages do not open with your own server while the VPN is on, go back to Automatic.
Which server name should I enter? We do not recommend third-party DNS servers; take the name from the provider’s site and enter it without “https://”.