No - Microsoft Edge does not come with its own DNS server, and it does not run a public resolver of its own. By default it uses your operating system’s DNS settings, the same ones every other program on the machine uses. What confuses people is the Secure DNS feature: Edge can send its lookups over DNS-over-HTTPS to a resolver you choose, independent of the rest of the system. So Edge can resolve names differently from the OS, without ever being a DNS server itself.
The question usually comes from a real symptom: a site loads in Edge but not in another app, or the other way around. That split is exactly what browser-level Secure DNS produces, and understanding it turns a mystery into a two-minute settings check.
Table of contents
- The default: Edge follows the operating system
- Secure DNS: DNS-over-HTTPS inside the browser
- Why Edge can resolve a site the rest of the PC cannot
- DoH always uses the built-in resolver
- How to check and change it
- How this fits the rest of the stack
- FAQ
The default: Edge follows the operating system
Out of the box, Edge resolves domain names using whatever DNS the operating system is configured to use - your router’s resolver, your ISP’s, or whatever you set manually in the network adapter. There is no Edge DNS server involved. A lookup for a site goes through the same path a lookup from any other application would.
This is why, most of the time, if a site resolves in Edge it resolves everywhere, and if DNS is broken system-wide, Edge breaks with everything else. The browser is a client of the system resolver, not a resolver itself.
So the plain answer to the question is no. The longer answer is the Secure DNS setting, which is the one thing that can make Edge behave differently from the rest of the machine.
Secure DNS: DNS-over-HTTPS inside the browser
Edge includes a feature called Secure DNS, which uses DNS-over-HTTPS (DoH). Instead of sending lookups as plain UDP that anyone on the path can read, DoH wraps them in an encrypted HTTPS connection to a DoH-capable resolver.
You will find it under Settings, Privacy, search, and services, Security, Use secure DNS. You can leave it on your current service provider or pick a specific DoH provider from the list.
The key point: this changes which resolver Edge talks to and how, but it still does not make Edge a DNS server. Edge is now a DoH client pointed at someone else’s DoH endpoint. The resolution work still happens on a server that is not Edge - it is just reached over an encrypted channel that the rest of your OS may not be using.
Why Edge can resolve a site the rest of the PC cannot
Here is the practical consequence. If Edge has Secure DNS enabled and pointed at a public DoH resolver, while the operating system uses a different resolver - say a local or corporate one - the two can genuinely disagree.
- A site blocked at the OS resolver but allowed by the public DoH one loads in Edge and nowhere else.
- A site on an internal network, resolvable only by the corporate resolver, loads everywhere except Edge, because Edge’s DoH provider has never heard of the internal name.
This split is the number one reason someone asks whether Edge has its own DNS. It effectively does have its own DNS path when Secure DNS is on. If a site works in Edge but not elsewhere, or vice versa, check the Secure DNS setting first - it is the cheapest thing to rule out.
DoH always uses the built-in resolver
One detail worth knowing: when Secure DNS is on, Edge uses its own built-in DNS client to perform the DoH request, rather than handing the lookup to the OS. This is by design and documented by Microsoft. It is why enterprise environments sometimes disable Secure DNS through policy - so that every lookup goes back through the managed OS resolver where filtering and logging live.
If you are on a managed machine and Secure DNS is greyed out or keeps reverting, that is policy, not a bug. The organization has decided all DNS should go through its own resolver, and it has turned off the browser’s ability to route around that.
For a personal machine, the setting is yours to choose. For a work machine, expect it to be controlled centrally.
How to check and change it
To see what Edge is doing:
- Open Settings, then Privacy, search, and services.
- Scroll to Security.
- Look at Use secure DNS.
If it is off, Edge is following the OS resolver - no separate DNS path. If it is on, note whether it is set to your current service provider or a specific DoH provider; the specific-provider case is what creates a resolution path independent of the OS.
To make Edge match the rest of the machine, turn Secure DNS off, or set it to use your current service provider. To deliberately encrypt Edge’s lookups and route them to a chosen resolver, turn it on and pick a provider. Either way, you now know what the setting actually does, which is more than the original question assumed.
How this fits the rest of the stack
DNS is the layer everyone forgets until a name resolves in one place and not another. The same class of question - which resolver answered, and why does one client disagree - shows up when you point a custom domain at a deployed app and the record has not propagated yet. Knowing where resolution happens is half of debugging it. The RunxBuild hosting calculator lays out the service, database, storage, and bandwidth as separate line items, and the RunxBuild dashboard is where the team watches deploys, logs, and restarts as they happen.
Useful related references:
- 500 Internal Server Error: The Version of the Answer That Actually Fixes One
- Claude Code MCP Server Setup: The Configuration That Actually Works After the First Restart
- 8GB or 16GB RAM: How Much Does Your Server Actually Need?
- Services on RunxBuild
FAQ
Does Microsoft Edge use its own DNS server?
No. Edge does not ship or run its own DNS server. By default it uses the operating system’s DNS settings. Its Secure DNS feature can route lookups over DNS-over-HTTPS to a resolver you choose, but that resolver is still a separate server, not Edge itself.
What is Secure DNS in Edge?
Secure DNS uses DNS-over-HTTPS to encrypt Edge’s domain lookups and send them to a DoH-capable resolver. It changes which resolver Edge talks to and protects the lookup in transit, but Edge remains a client - the resolution still happens on an external server.
Why does a site load in Edge but not in other apps?
Most likely Edge’s Secure DNS is pointed at a different resolver than the rest of your system. If that resolver can answer a name the OS resolver cannot, or is blocked differently, Edge and other apps disagree. Check Settings, Privacy, search, and services, Security, Use secure DNS.
Does Edge Secure DNS use the operating system resolver?
No. When Secure DNS is enabled, Edge uses its own built-in DNS client to make the DoH request rather than handing it to the OS. That is why organizations sometimes disable the feature by policy, so all lookups go through the managed OS resolver.
How do I make Edge use the same DNS as the rest of my PC?
Turn Secure DNS off, or set it to use your current service provider, under Settings, Privacy, search, and services, Security. That makes Edge follow the operating system’s DNS configuration like every other application.