Two well-known VPN brands are stepping back from running free public DNS resolvers. If you pointed a router or phone at them, today is a good day to check your settings.
DNS is the internet’s phonebook, and it is also one of the quietest privacy leaks in everyday life. Every time you visit a website, your device asks a DNS resolver to translate the name into an address, which means whoever runs that resolver can see a running list of the sites you look up. For years, a handful of privacy-minded VPN companies offered free public resolvers for people who wanted an alternative to their internet provider’s default servers.
That landscape is shrinking. TechRadar reported that Mullvad is discontinuing its public encrypted DNS service, with a deadline of November 2, 2026 for manual users to migrate, and that Surfshark is shutting down its free Public DNS service after just 19 months, citing limited adoption. Neither change affects people who simply use those companies’ VPN apps, but they can break setups that were configured by hand. Because the Mullvad deadline has now passed, anyone who has not migrated should check their devices.
What exactly is closing?
Mullvad had offered its DNS over HTTPS servers as a free public service for people who were not connected to the VPN. DoH encrypts the request between your device and the resolver so that people on your local network cannot easily read it. In its announcement, as relayed by TechRadar, Mullvad said that running a privacy-focused public DNS service is a highly specialized undertaking, and that the Quad9 Foundation is the leader in that field. Rather than duplicating that work, Mullvad said it will put resources toward financially supporting Quad9 instead.
Surfshark’s Public DNS is a separate product with a similar purpose. The details we could confirm come from the headline of TechRadar’s coverage: the service is being shut down after 19 months, with the company citing limited adoption. We were not able to review the full migration guidance for Surfshark’s service, so if you used it, check Surfshark’s own announcement for exact dates and steps.
Who needs to take action
The impact depends entirely on how you were using the service. Mullvad’s own guidance, as summarized by TechRadar, breaks users into groups. The good news is that most people will be fine. The table below shows the picture.
| If you… | What happens | What to do |
|---|---|---|
| Use the Mullvad VPN app | Nothing changes; traffic uses Mullvad’s internal DNS routing while connected | No action needed |
| Use Mullvad Browser with default DoH or the ad-blocking variant | Browser migrates automatically to Quad9 | No action needed |
| Use Mullvad Browser with a custom variant (base, extended or family) | You must change DoH settings back to the default | Reset DoH to default in the browser |
| Installed a Mullvad DoH profile on iOS or macOS | The profile stops working after shutdown | Replace it with a Quad9 profile for that platform |
| Hard-coded Mullvad DoH servers in a router or operating system | Name lookups will fail or fall back unpredictably | Enter Quad9’s addresses using Quad9’s configuration guides |
How to migrate in about ten minutes
Quad9 is run by a nonprofit foundation, and its widely used resolver address is 9.9.9.9. Because settings screens differ across devices and Quad9 updates its guides over time, follow Quad9’s official configuration instructions for your exact platform rather than copying numbers from a blog post, including ours. The outline below covers the usual route.
- Make a list. Check your router, your computers, your phones, and any browsers where you set DNS manually.
- Find old entries. Look in network settings for any mention of Mullvad’s DNS addresses or hostnames, and in iOS or macOS for installed DNS profiles.
- Replace with Quad9. Use Quad9’s official guides to configure encrypted DNS for each platform. Prefer the router for whole-home coverage if your router supports encrypted DNS.
- Test. Visit a handful of sites, then run a DNS leak test to confirm that lookups go where you expect.
- Document it. Write down what you changed so the next provider shutdown is a five-minute job.
Why are VPN companies retreating from free DNS?
Mullvad’s explanation is about focus: running a secure, fast, privacy-respecting resolver at scale is hard, and a nonprofit that specializes in it can do the job better. That tracks with the company’s history. TechRadar notes that Mullvad has a record of retiring legacy features in the name of security and simplicity, such as removing port forwarding and ending OpenVPN support on desktop to steer users toward WireGuard.
Surfshark’s stated reason, limited adoption, points to a different kind of pressure. A free public service has real costs: servers, bandwidth, abuse handling, and engineering attention. If few people use it, the business case for continuing is thin. This is a reasonable inference rather than a confirmed account from either company, but it fits a broader pattern in which VPN brands trim side projects to concentrate on their core subscription product.
DNS privacy basics worth remembering
A VPN and encrypted DNS solve different problems
When you connect to a VPN, your DNS lookups normally travel through the encrypted tunnel to the provider’s resolvers, which is why Mullvad calls its public DoH servers unnecessary for subscribers. Encrypted DNS on its own, such as DoH without a VPN, hides your lookups from the local network but still reveals them to the resolver you chose. Neither approach hides the IP addresses you eventually connect to.
What to look for in a resolver
What this means for VPN shoppers
If you are choosing a VPN, the lesson is not to avoid providers that close side products. It is to separate the core service from the extras. Look at how well the provider maintains its main apps, whether it publishes independent audits, and how it handles change: Mullvad gave users roughly two months of notice and clear migration instructions, which is exactly what a responsible shutdown looks like. Weak communication around retirements is a better red flag than the retirement itself.
For everyone else, this is a prompt to do a ten-minute audit of the invisible plumbing of your network. DNS settings tend to be configured once and forgotten, which is exactly why they cause problems years later.
