Using DNS over HTTPS When a Website Appears Blocked
DNS over HTTPS (DoH) can sometimes help when a website appears unavailable because the DNS resolver on a network is returning an incorrect, filtered, or incomplete answer. It is not a universal way to reach a blocked website. A website can be restricted at several layers, so changing DNS only helps when DNS is part of the problem.
What DNS over HTTPS changes
DNS translates a domain name such as example.com into an IP address. Traditional DNS requests are usually sent to the resolver selected by your router, internet provider, or network administrator. DoH sends that lookup through an encrypted HTTPS connection to a DNS resolver instead. This can reduce casual observation or modification of the lookup between your device and that resolver, and it can let a browser use a different resolver from the one configured for the network.
It does not encrypt the website connection by itself, hide your public IP from a website, or change rules enforced beyond DNS. Think of it as a different path for finding an address, not a replacement for every network control.
When it may help
DoH can be worth a normal troubleshooting check when one network cannot resolve a domain but another can, when a resolver returns an obvious error page or old address, or when a captive portal has left DNS in an unusual state. First use DNS Lookup to compare the public records you expect with the answer your device receives. If the domain does not resolve anywhere, changing resolvers is unlikely to fix the site itself.
A browser may offer a setting called Secure DNS, DNS over HTTPS, or encrypted DNS. Enable it only if it fits your network policy, select a trustworthy resolver where the browser offers a choice, then retry the site in a fresh tab. On many devices, operating-system encrypted-DNS settings affect more applications than a browser setting; browser documentation and system settings are the right source for the exact steps for your version.
When changing DNS will not help
DNS is only one possible control point. A site may be unavailable because its IP address is blocked, a firewall rule applies, traffic is filtered using SNI or TLS information, or a service has its own access rule. Parental, school, workplace, and enterprise controls may be intentional safety or administrative measures. Regional or legal restrictions can also be enforced in ways that changing DNS does not affect. Do not use this guidance to evade lawful controls or a network's acceptable-use policy; ask the administrator when access is needed for a legitimate purpose.
Browser DoH and system encrypted DNS are not identical
Browser Secure DNS can apply only to lookups made by that browser. Other applications may continue using the resolver selected by the operating system or router. An operating-system encrypted-DNS setting can have wider reach, but its support and behavior vary by device and managed-network policy. Internal names used by a workplace, school, or home lab may require the organization's resolver, so replacing it can make legitimate services unavailable.
Captive portals are another exception. Hotels, airports, and public Wi-Fi networks sometimes depend on an initial DNS response to show their sign-in page. If that page does not appear, temporarily following the network's documented connection process is more appropriate than repeatedly changing encrypted-DNS settings. Once connected, restore the configuration that suits the network and your privacy requirements.
A practical troubleshooting sequence
Start by checking the exact address and error message. Try the site on a permitted second network, such as your own mobile connection, to distinguish a site outage from a local network issue. Confirm that the date, time, and browser are current. Use DNS Lookup to review public records, then enable DoH in one browser or use a permitted encrypted-DNS setting and test again. If the problem is specific to a managed network, report the domain, time, and error to its administrator rather than repeatedly changing settings.
DoH is related to DNS privacy but it does not prove that DNS requests never take another path. Read What Is a DNS Leak? for the distinction, and use Privacy Check for the browser and network signals this site can inspect. More context is available in the Guides hub.
Frequently asked questions
Does DNS over HTTPS unblock every website?
No. It may help only when DNS resolution is the relevant issue. IP, firewall, TLS, account, policy, and legal restrictions can still apply.
Is DoH the same as a VPN?
No. DoH encrypts DNS lookups to a resolver. A VPN changes how broader network traffic is routed, subject to its own configuration and limitations.
Should I leave DoH enabled?
That depends on your device, resolver choice, and network requirements. Managed networks may need their own resolver for internal names or security controls.
Can a DNS provider see my browsing?
A resolver can process the domain names it is asked to resolve. DoH encrypts the path to that resolver; it does not make the resolver unaware of the lookup or hide the destination from the website you visit.