Android VPN Connected but Chrome Cannot Find Sites? Secure DNS Checks

Locate the failing layer

Google distinguishes automatic Secure DNS, which can fall back to unencrypted lookup, from a custom provider that does not use that fallback. An unreachable custom resolver can therefore break browsing without breaking all connectivity. Encrypted DNS protects lookup, not all traffic.

Fix the route and change one setting

1. Record URL, exact error, time and Chrome version without account details or tokens.
2. In Android Chrome Settings, Privacy and security, inspect Use secure DNS. Record the provider and leave system Private DNS unchanged.
3. Keep network and VPN route fixed. For a custom provider, temporarily select the current provider or automatic option and retry the same public page.
4. If temporarily disabling Secure DNS for comparison, understand Chrome may no longer encrypt the lookup. Restore it afterward rather than treating disabling as a speed fix.
5. Restore the original provider and repeat. If failure follows that provider, contact its support. Ask the administrator about managed settings.

Interpret the comparison

A Chrome-only recovery following a DNS change points to resolver configuration, not proof that every route service works. If all apps fail, return to basic connectivity checks. Do not use unknown resolvers or disable certificate checks. This guide neither claims a custom-DNS feature in Yunbao nor reports route speed tests.