One browser reports a DNS error while another works: compare the resolver path

Separate a browser-specific secure-DNS path, VPN or proxy policy, caching and an authoritative website problem without changing every device’s DNS.

WireTrace UK editorial team · Published · 7 min read · Updated 21 November 2026

In this guide
  1. Record a resolution error accurately
  2. Keep the device and network fixed
  3. Inspect the supported resolver settings
  4. Compare results within their limits
  5. Verify the real page after the change
  6. Comparison record
  7. Questions
  8. Sources and scope

Choose the website symptom in the free connection troubleshooter and record the browser, exact DNS error and whether the same address opens in a second browser.

Two devices for comparing the same failing website — AI-generated scene illustration
Two devices for comparing the same failing website. AI-generated scene illustration; not a measured result or an exact wiring reference.

The question: Chrome says the site cannot be found, but another browser opens it. Should I change DNS on the router?

Record a resolution error accurately

Write down the exact public hostname and browser error, plus the time and whether other sites work. Distinguish name resolution from a TLS/certificate warning, HTTP error, sign-in failure or connection timeout. These are different stages. A page that says “server not found” gives a direction for investigation, but it does not prove which resolver or network component failed.

Check the address carefully using a trusted source. Do not follow a typo into an unrelated site, and do not use private company hostnames in public diagnostic services. Keep the failing URL’s path, query strings and tokens out of shared notes when they contain private information.

Keep the device and network fixed

Try the same ordinary public hostname in a second browser on the same device. Record whether a work VPN, proxy, managed profile, extension or security product applies differently. A phone comparison is useful too, but first confirm it uses the intended Wi-Fi and not mobile data; otherwise it changes several parts of the path.

Browsers and operating systems can retain cached results and use different DNS mechanisms. One browser opening a cached page is weaker evidence than a fresh permitted request to the actual site. Note whether the problem concerns one hostname or many. Avoid repeatedly clearing all browser data before recording the differences, because that can remove useful state and sign-ins.

Connection equipment before a controlled DNS-path comparison — AI-generated scene illustration
Connection equipment before a controlled DNS-path comparison. AI-generated scene illustration; not a measured result or an exact wiring reference.

Inspect the supported resolver settings

Modern browsers may use encrypted DNS through a selected provider, while another browser uses the operating system’s configured resolver. The exact behaviour depends on browser version, management policy and fallback rules. Cloudflare’s current troubleshooting material separates ordinary resolver tests from DNS-over-HTTPS and DNS-over-TLS checks for this reason.

Record the setting before changing it. On a managed device or work VPN, follow the organization’s policy; internal names may depend on its resolver. Do not disable security or bypass an intentional filtering policy as a troubleshooting shortcut. If a comparison is permitted, change one resolver-related setting for one test and restore it afterwards unless a supported permanent change is intended.

Compare results within their limits

A supported operating-system lookup can show whether that configured resolver returns an answer, but it may not follow the same path as the failing browser. A public resolver result can show how that service sees a public name; it does not automatically describe a private corporate zone or the browser’s current cache. Label each method and time.

If multiple independent permitted paths report the same public-name problem, inspect the website or domain operator’s status and support route. If only one browser path fails, review its configured provider, policy and exact error. Changing router DNS for every device can be disproportionate when only one managed browser is affected. Do not substitute an arbitrary IP address into an HTTPS URL as a universal bypass.

Recording an exact browser error and comparison conditions — AI-generated scene illustration
Recording an exact browser error and comparison conditions. AI-generated scene illustration; not a measured result or an exact wiring reference.

Verify the real page after the change

ObservationNext useful check
Only one browser fails on the same deviceCompare browser resolver, profile and policy.
Only the work-VPN path failsUse the approved internal DNS/support route.
Several independent paths fail for one public nameCheck the website/domain operator’s current status.
Names resolve but HTTPS failsInvestigate the subsequent connection or certificate stage.

Open the original page and complete the intended ordinary task after a supported change. Keep the exact change and rollback setting. A faster package, cable tester or extra Wi-Fi node does not normally address a browser-only resolver mismatch. The useful purchase decision here is often that no new hardware has yet been justified.

Keep a comparison record

Label each result by browser or lookup tool, resolver context and time. Keep the exact public hostname but remove private URL paths and credentials before sharing the record.

Worksheet fields: Time; Public hostname; Exact error stage; Browser and profile; Network; VPN or proxy; Secure-DNS context; Second-browser result; Permitted lookup result; Change and rollback.

Accept the result when: The original website task works through the intended supported resolver path without weakening the required security or work policy.

Download the blank CSV worksheet

Questions that change the next step

Does a successful nslookup prove the browser should work?

No. It tests a particular resolver path at that time. The browser may use a different encrypted-DNS provider, cache, profile or policy.

Should I publish my router and work DNS configuration?

Share only the relevant redacted evidence through the appropriate support channel. Private hostnames, internal addresses, tokens and account information can be sensitive.

Continue with the evidence you have

No new cable-test instrument is established as necessary by a browser, NAT or discovery result. Use the supported settings and task comparison first.

Questions before you change anything

Why does one browser report a DNS error while another works?

They may use different secure DNS, resolver cache, proxy settings or browser policies. Compare the exact hostname and error before changing the router for every device.

Does changing the router DNS change every browser?

Not necessarily. A browser’s DNS-over-HTTPS setting, managed configuration, VPN resolver or extension can select a different path. Check the affected browser’s supported settings and workplace policy.

Should I flush DNS or clear all browser data?

Start with a private window, fresh profile, system lookup and browser-specific cache where supported. Preserve saved information unless a broader reset is justified by the narrower comparison.

Could this be a certificate problem rather than DNS?

Read the exact error code, hostname spelling, system clock and certificate status. Do not bypass a browser security warning; a page failing to open does not make every error a name-resolution failure.

What evidence should I collect before contacting support?

Record browser versions, resolver choice, same-site comparison and failure time. Remove private hostnames and tokens from shared logs. A new cable tester cannot explain two browsers using different resolver policies.

Community scenarios behind these checks

Questions and source links reviewed 21 November 2026. The answers apply the limits described in this guide; they are not a test of your equipment.

Sources and scope

The references support the measurement principles and device-specific checks. This guide organises them into a practical comparison sequence. Calculations are examples; the AI-generated scene illustrations are not test captures. Use the exact device documentation and the site methodology.

Reader questions that informed this update: Reddit: reader discussion. Individual reports help identify questions; answers above use the technical references in this guide. One Reddit original post was deleted; only its displayed title and replies were available.

Details worth checking

What if a private window changes the result, or I see 403 instead?

A private window can change cookies, extensions and sign-in state without changing every DNS setting. Compare a clean supported browser profile only after saving the existing setup. An HTTP 403 means a server refused the request; keep its reference ID and account context. It should not be relabelled as a DNS error merely because another browser succeeds.

Explain your own result

Replace the brackets with observations you actually made. Leave unknowns as “not checked”. This draft is written for this guide; it is not a quotation or an automatic diagnosis.

On the same device/network, [browser] returns [DNS error] for [public hostname], while [browser] gives [result]. System lookup [resolver/result], secure-DNS/VPN/proxy [permitted context], private-window test [result]. Help compare resolver paths without assuming a router-wide DNS change is the answer.

Copying stays on your device. Remove passwords, account numbers and private network details before sharing.

Reader questions that informed this update: Reddit: reader discussion. Individual reports help identify questions; answers above use the technical references in this guide. One Reddit original post was deleted; only its displayed title and replies were available.