What's happening
Surfshark's support article on the service, updated November 12, carries a retirement notice. It says the company will stop the service "starting November 24th, 2026" so it can focus on its server network, connection speed and reliability. The same notice tells anyone who set up the DNS manually to switch to another resolver, and it names Google and Cloudflare as examples. The notice gives no shutdown time or time zone, so treat the morning of the 24th as the real deadline.
The company's explanation is simple: not enough people used it. Launched in late April 2025 as a free, no-logs alternative to internet service providers' default DNS resolvers, the service is closing after 19 months. A Surfshark spokesperson told TechRadar that it "saw limited adoption." Surfshark has not published user numbers. The spokesperson told TechRadar that the company would rather put its resources into improvements that benefit most of its users than into a service used by a relatively small group.
Surfshark's own blog confirms the launch timing. Its June 2025 quarterly update announced the public DNS servers and said no active subscription was needed. That post also warned that DNS is not a replacement for a VPN and does not give the same level of security.
The short version: the free resolver goes dark on November 24. Surfshark VPN subscribers can ignore this. Anyone who entered the addresses by hand needs to act.
Who is affected
- Paid Surfshark VPN subscribers: Not affected, according to TechRadar. The VPN sends DNS queries through its encrypted tunnel by default. When the DNS service launched, Surfshark engineer Karolis Kaciulis told the outlet that a separate DNS setup was redundant for VPN users.
- Anyone who configured Surfshark Public DNS manually: The shutdown mainly affects non-subscribers and others who entered Surfshark's DNS addresses directly into their routers or devices. Once the servers go offline on November 24, those devices will not be able to load websites until their DNS settings are switched to automatic or changed to another resolver, such as Quad9.
- People who moved over from SmartDNS: This group gets hit twice. Earlier this year Surfshark retired its SmartDNS feature for smart TVs and consoles, saying demand for this feature was very limited. In the SmartDNS retirement notice, Surfshark told those users to use Surfshark Public DNS (194.169.169.169), or you can choose any other DNS provider you prefer. If you followed that advice, your TV or console now depends on the service that is shutting down. Check it alongside your PCs.
TechRadar's warning that your "connection" will drop needs one correction. Your network link stays up; only name lookups fail. Your PC will still connect, and you can still reach sites by IP address, but websites won't load by name. On Windows that usually shows up as browser errors that look like a DNS failure. Network diagnostics may also say the DNS server isn't responding.
Which addresses to look for
Surfshark's documentation lists these endpoints. If any of them appear in your settings, you need to replace them:
| Type | Surfshark endpoint being retired |
|---|---|
| IPv4 | 194.169.169.169 |
| IPv6 | 2a09:a707:169:: |
| DNS-over-HTTPS | [url]https://dns.surfsharkdns.com/dns-query[/url] |
Encrypted DNS settings are easy to miss. Surfshark's support page says the resolver supported DNS-over-TLS, DNS-over-HTTPS and DNS-over-QUIC. A device with the plain IPv4 field set to automatic might still have the DoH template entered somewhere else.
How to fix it on Windows
Surfshark's support page uses the classic Control Panel route. To undo the setup that way:
- Open Control Panel > Network and Internet > Network and Sharing Center.
- Click Change adapter settings.
- Right-click the active connection (Wi-Fi or Ethernet) and choose Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Choose Obtain DNS server address automatically, or enter the resolver you're switching to. Click OK.
- Do the same for Internet Protocol Version 6 (TCP/IPv6). Surfshark's instructions included an IPv6 address, but its Windows steps only open the IPv4 properties, so it's easy to have changed one protocol and forgotten the other.
On Windows 11, the Settings app is usually quicker. The following steps come from general Windows knowledge, not from Surfshark's documentation:
- Go to Settings > Network & internet, then select Wi-Fi or Ethernet. For Wi-Fi, open the connected network's properties or Hardware properties.
- Next to DNS server assignment, click Edit.
- Switch to Automatic (DHCP), or keep Manual and enter a new resolver. If you used encrypted DNS, also update the DNS-over-HTTPS setting for each address.
- Repeat for every adapter you use. A laptop that moves between Wi-Fi and Ethernet keeps separate settings for each.
Check your work: open Command Prompt and run ipconfig /all. The "DNS Servers" lines should no longer show 194.169.169.169 or 2a09:a707:169::. Then run ipconfig /flushdns to clear cached lookups, and run nslookup against any domain to confirm a working resolver answers.
Check your browser too: Edge, Chrome and Firefox each have their own secure DNS setting. In Edge it's under Settings > Privacy, search, and services > Use secure DNS. If you entered Surfshark's DoH URL as a custom provider there, change it, or the browser will keep using the dead resolver even after Windows is fixed.
Routers, phones and the devices you forgot about
Surfshark also published manual setup steps for macOS, Android, iOS and routers. Reversing them follows the same paths:
- Router: Log in to the admin page (Surfshark's guide mentions common addresses such as
192.168.1.1or192.168.0.1) and find the DNS fields under the Internet or WAN settings. Replace the Surfshark entries, save, and reboot if the router asks. This is the most important one to fix. Devices on your network typically get their DNS settings from the router, so one stale entry there can break name lookups for every device in the house. - Android: Surfshark's steps had users set Wi-Fi to Static to enter DNS. Switch back to DHCP or update the fields. Also check Private DNS if you set a hostname there.
- iOS: Under the Wi-Fi network's Configure DNS, switch back to Automatic or replace the manual servers.
- macOS: Remove the Surfshark entries from the DNS tab in the network connection's Details pane.
- Smart TVs and consoles: Surfshark's SmartDNS retirement notice already told users to choose Set automatically where available. That's still the simplest fix.
Picking a replacement resolver
Surfshark names Google and Cloudflare. TechRadar suggests Quad9 as a privacy-focused option. Here is how the main options compare, based on general industry knowledge:
- Automatic/ISP DNS: Needs no setup, but your provider sees your lookups unless you add encryption elsewhere.
- Cloudflare or Google: Fast, widely supported, and on Windows 11's list of providers with built-in DNS-over-HTTPS support.
- Quad9: A nonprofit that blocks known malicious domains. One caveat for readers in France: a DNS comparison guide from CaptainDNS says Quad9: unavailable in France from November 24, 2026 (Quad9 announcement). That is the same day Surfshark shuts down, so French users switching to Quad9 should check that before committing.
In a business or school network, a home-grown resolver change on a managed laptop may conflict with policy-pushed DNS. Ask IT before changing anything.
The bigger picture: VPN companies are getting out of free DNS
Surfshark is the second VPN provider this autumn to drop a public resolver. Mullvad VPN made a similar call in September 2026, closing its own public encrypted DNS servers ahead of a November 2 deadline to sponsor the non-profit Quad9 Foundation instead. The reasons differ, though. Mullvad's case was that its VPN already handles DNS internally, and it chose to fund a nonprofit resolver. Surfshark cites low uptake and a shift of engineers to its own infrastructure, and has not said it will support or move users to any other resolver.
This is also the second DNS product Surfshark has retired in 2026, after SmartDNS. Both times the company gave the same reason: limited demand, with resources redirected to the core VPN. That's a reasonable business decision. Free infrastructure costs money, and a no-logs resolver doesn't sell subscriptions. But giving users four days' notice in the news cycle, plus a support-page note posted 12 days before shutdown, is a short runway for a service people were encouraged to hard-code into routers. That includes former SmartDNS users whom Surfshark itself pointed to this service only months ago.
The general lesson for anyone hard-coding DNS settings: a free resolver can disappear like any other free service. Write down which devices you changed, keep a second resolver configured as a fallback, and check your settings now and then. Then November 24 is just another Tuesday.
Bottom line: if 194.169.169.169, 2a09:a707:169:: or Surfshark's DoH URL appears anywhere on your PCs, router, phone, browser or TV, replace it before November 24. It takes about five minutes per device, and it saves you troubleshooting a "broken internet" later.
References
- Surfshark is shutting down its free Public DNS service after just 19 months, citing 'limited adoption' TechRadar · 2026-11-20T17:02:39+00:00
- Public DNS Comparison Guide: Cloudflare, Google, Quad9, NextDNS... captaindns.com
- What is Surfshark public DNS? – Surfshark Customer Support support.surfshark.com