The Corporate Network Conflict
Google Chrome includes a privacy feature called “Use secure DNS” (also known as DNS-over-HTTPS, or DoH). Traditionally, when you type a website address, your browser sends a plain-text request to your Internet Service Provider’s DNS server to translate the name into an IP address. Anyone snooping on your network can see exactly which sites you are visiting. Secure DNS encrypts these requests, bypassing your ISP and sending them securely to providers like Cloudflare or Google Public DNS.
While this is fantastic for privacy on a public coffee shop Wi-Fi network, it is often a disaster in corporate environments. Many enterprise networks use internal, custom DNS servers to route traffic to private intranet sites (e.g., portal.company.local). Because Chrome’s Secure DNS encrypts and sends requests to the outside world, it completely bypasses the local corporate DNS. This results in the browser failing to load any internal company websites. To fix intranet routing issues, you must disable Secure DNS.
How to Disable Secure DNS (DoH)
You can force Chrome to use your operating system’s default DNS settings.
- Open Google Chrome.
- Click the three vertical dots in the top-right corner and select Settings.
- In the left-hand sidebar, click on Privacy and security.
- In the main pane, click on Security.
- Scroll down to the “Advanced” section.
- Look for the toggle switch labelled Use secure DNS.
- Toggle the switch to the Off position.
Chrome will immediately revert to using standard, unencrypted DNS queries based on the settings provided by your Windows or macOS network adapter, restoring your ability to resolve internal corporate domains.