Get One Month of Starlink FreeSPECIAL OFFER: GET A FREE MONTH OF STARLINK >
Modern laptop and smartphone on a textured wooden desk, capturing the essence of contemporary technology.

Why Your Browser's Secure DNS Can Bypass Router DNS Settings

Troubleshooting & Fixes

Back to Troubleshooting & Fixes

Changing DNS on a router does not necessarily change how every browser resolves names. A browser can use its own encrypted resolver, making device and router tests appear to disagree.

Work through the setup

Step 1

Check whether the problem affects one browser, all browsers or every device. Keep a working browser available while testing.

Step 2

Record the router's configured DNS and the affected browser's Secure DNS setting. Note any managed-device restrictions before making a change.

Step 3

Compare automatic mode with the chosen custom provider using the browser's documented controls. Change only that setting for the test.

Step 4

Try the same hostname again and record the precise error. Successful DNS lookup is different from successful HTTPS connection.

Step 5

If you use household filtering, test that it still behaves as intended. Do not bypass work or school policy on a managed device.

Step 6

Restore the previous setting if it does not improve the symptom. Keep a note of which resolver path produced each result.

Worked example

Suppose the router uses your household DNS filter, yet Chrome resolves a blocked test domain differently from another application. Check whether Chrome has a custom Secure DNS provider before changing the router again. Compare automatic and custom modes briefly on a device you control, then return to the intended policy. If the device is managed, provide the discrepancy to its administrator instead of trying to bypass that management.

Interpret the result

  • Only one browser differs: Review that browser's resolver path.
  • Every device differs: Check the shared router or resolver.
  • A managed setting blocks changes: Ask the administrator for the approved test.

Checks and limitations

Google documents different fallback behaviour for automatic and custom Secure DNS modes. This is a browser configuration issue to investigate, not proof that the dish is ignoring your router.

Why does Chrome ignore the DNS server I set on my Starlink router?

Chrome may be using a custom Secure DNS provider instead of the router's advertised resolver. Check the browser setting and any management policy, then compare one change at a time. Restore the original setting if it does not fix the problem.

Sources and review

Official documentation for this guide

Reviewed: 11 November 2026. The practical sequence and worked example are Starlink Tips editorial guidance. Check current instructions for your hardware, software and country.

Illustrative photograph: Modern laptop and smartphone on a textured wooden desk, capturing the essence of contemporary technology. Credit: Hasan Albari.