Smart DNS on Your Router: Setup That Covers Every Device

By smartdnscomparison editorial desk · updated 2026-10-04 · facts checked 2026-10-04

table of contents

1. Why the router is the best place
2. What you need before you start
3. The generic recipe
4. Brand click-paths
5. Test it properly
6. Devices that ignore the router
7. Dynamic DNS: the changing-IP problem
8. Fallback DNS entries: what to put in slot two

Why the router is the best place

Set the resolver once on the router and every device that joins the network inherits it: the Smart TV you cannot configure comfortably, the console buried in settings menus five levels deep, the old Apple TV, the kids' tablets. No device list to maintain, nothing to repeat after an app reset [1].

Two honest limits. First, DNS on the router is household-wide - you cannot unblock just the TV while keeping the laptop's resolver default (device-level settings override DHCP anyway [see below]). Second, some platforms ignore it: Chromecast and Roku generations carry hardcoded Google DNS and talk to 8.8.8.8 regardless of what your router hands out [4].

What you need before you start

• The provider's two resolver IPs - every operator hands out a primary and a secondary. Secondary differs for a reason: it is your fallback, not a free slot for Google's resolver (see [Fallback entries](#fallback-dns-entries-what-to-put-in-slot-two)).
• Admin access to the router web interface - the address is usually 192.168.0.1, 192.168.1.1, fritz.box or a vendor domain, with the credentials on the router sticker.
• A note of the current DNS settings - write down what is configured now, so removal takes thirty seconds.
• The device list you actually stream on, to verify afterwards.

The generic recipe

Every router brand buries the fields in a different menu, but the change itself is identical:

1. Open the router's web interface in a browser and log in.
2. Find the DNS fields - they live either under DHCP/LAN settings (what devices are told to use) or under WAN/Internet settings (what the router itself uses). Both work; the DHCP one covers more devices.
3. Replace both resolver IPs with the provider's primary and secondary. Leave search domains and other optional fields alone.
4. Save and reboot the router if asked.
5. Reconnect a streaming device (or restart it) and check the provider dashboard's DNS status.

If the dashboard check stays red, work down the troubleshooting list below - the causes are the same everywhere: wrong entry, IPv6, DoH, Private Relay [8].

Brand click-paths

FRITZ!Box: Internet > Account Information > DNS Server (IPv4, and IPv6 separately). Newer FRITZ!OS versions also accept DNS-over-TLS servers - Control D documents both paths and recommends DoT where available [1].

ASUS: Web GUI > LAN (or Advanced Settings > LAN > DHCP Server) > DNS Server fields (WAN > Internet Connection also has them). TP-Link: Advanced > Network > Internet > Advanced DNS, or DHCP > DHCP Settings depending on firmware. Both brands carry IPv6 pages on the same interface - that is also where you disable IPv6 if it fights the setup [9]. Netgear: BASIC > Internet > Domain Name Server (DNS) fields.

For every other brand - Mikrotik, DD-WRT, Linksys, D-Link, FreshTomato, GL.iNet - both Control D [2] and Unlocator [4] publish per-model guides with screenshots.

Test it properly

1. Dashboard check. Operators show a live check (Unlocator: three green marks). Red means the device is not using their resolver - fix before debugging the streaming side [8].
2. Flush the cache. Windows: ipconfig /flushdns. macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Otherwise restart the device [6].
3. Turn off name-bypassing features on the test device: browser secure DNS [7], iCloud Private Relay [8], adblocker extensions that resolve on their own [8].

Devices that ignore the router

Chromecast (all generations) and Roku have Google DNS hardcoded; the device queries 8.8.8.8 no matter what DHCP said [4]. The documented fix happens on the router: a NAT/iptables rule that redirects traffic addressed to 8.8.8.8 and 8.8.4.4 to the provider's own IPs [4]. Unlocator keeps per-router recipes (ASUS, FritzBox, Mikrotik, Netgear, OpenWRT, TP-Link and more) [4]; the trick covers Roku and Chromecast Gen 1+2 outright, Gen 3/Ultra need the redirect variant [4].

IPv6 is the quieter saboteur: if the network prefers IPv6 DNS servers, your IPv4 entries never get used [8][9]. Either disable IPv6 on the router or use a provider mode that answers across stacks [2].

Dynamic DNS: the changing-IP problem

Router setup does nothing about the other chore: your public IP. Providers authorize households by IP, and when the ISP rotates yours, streams fail with an "IP not recognized" state until you re-activate in the dashboard [3].

The automation: register a Dynamic DNS hostname (router support is built into most brands), add the hostname to the provider account, and the provider keeps the authorization fresh by polling the hostname - Unlocator checks every ten minutes [3]. Providers that carry this (live data below) are worth checking before you buy if your ISP rotates aggressively:

Live values from our database - details and caveats in each review. "Visit" links may be affiliated.

A related trap is ISP-side DNS hijacking: some providers intercept port 53 regardless of your settings. The documented workaround redirects all port-53 traffic to the provider's alternative port on a capable router [10]; the clean alternative is a VPN, which an ISP cannot rewrite (comparison).

Fallback DNS entries: what to put in slot two

• Provider's secondary resolver - the intended use, designed to behave identically to the primary [4].
• A second Smart DNS provider - works, but region routing and channel lists differ; verify both.
• 8.8.8.8 / 1.1.1.1 - solves outages, defeats the trick: any device that prefers the fallback sees no unblocking at all. Some operators publish specific "block Google DNS" guides precisely because of this [4].
• Leaving it empty - safest for streaming devices; the device simply retries the primary.

For the device-level version of this walkthrough, the Smart TV guide covers Samsung, LG and Android TV menus - and if your ISP hub hides the DNS field entirely, that is where the workaround lives [5].

FAQ

Should I set Smart DNS on the router or on each device?

On the router, if it lets you. One change covers the TV, consoles, boxes and laptops, and you never repeat it. Set DNS per device only when the router blocks it (some ISP-locked hubs) or when you want only one device affected.

What do I put in the second DNS slot?

The provider's secondary resolver. Never Google's 8.8.8.8 - it resolves everything perfectly and is in no position to unblock anything, and some devices will prefer it over your primary.

Do I need to reconnect devices after changing router DNS?

New or reconnecting devices pick up the new servers immediately. Already-connected devices keep the old lease - reboot them, toggle Wi-Fi, or wait for the lease renewal.

Why is my provider's dashboard still showing a red DNS check?

In rough order of likelihood: a typo in the entries, IPv6 servers preferred over your IPv4 settings, browser DoH resolving names elsewhere, or iCloud Private Relay on an Apple device [8].

Does router DNS affect guest Wi-Fi and IoT devices?

It affects everything that uses DHCP from that router, which is usually every network it serves. If your router supports per-network DNS, you can exclude the guest network.

Can I set Smart DNS and still use DoH in my browser?

Not both at once on the same machine. Browser DoH sends lookups over HTTPS to its own resolver, bypassing your Smart DNS entries entirely [7].

My router has no DNS field. What now?

ISP-locked hubs often hide the field (Sky Hub is the classic UK case [5]). Alternatives: device-level DNS on the things that matter, a DMZ/hotspot workaround, or your own router in bridge/wired mode.

Is DNS on the router faster than a VPN on the router?

Different tools. Router Smart DNS adds no encryption overhead and stays set-and-forget; router VPN needs compatible firmware and routes the whole house through one exit country compare them.

How does the dynamic DNS updater work?

You register a Dynamic DNS hostname with the provider; the provider re-checks the hostname periodically (Unlocator every 10 minutes) and keeps your authorization current when your ISP rotates your IP [3].

Will this change the DNS for my phone away from home?

No. Router DNS applies to your home network only. On the road, your phone uses the local network's resolver - which is why travelers configure Smart DNS on the device or use a mobile profile.

Sources

1. Control D - FRITZ!Box router guide (DoT and legacy DNS) - accessed 2026-10-04
2. Control D - IPv4/IPv6 compatibility mode - accessed 2026-10-04
3. Unlocator Support - Using Dynamic DNS to update your IP - accessed 2026-10-04
4. Unlocator Support - How to block Google DNS on router - accessed 2026-10-04
5. Unlocator Support - I can't change DNS on my Sky Hub - accessed 2026-10-04
6. Unlocator Support - How to clear DNS cache - accessed 2026-10-04
7. Unlocator Support - Disable DoH on Firefox and Chrome - accessed 2026-10-04
8. Unlocator Support - Red DNS checkmark troubleshooting - accessed 2026-10-04
9. Unlocator Support - Disable IPv6 on TP-Link router - accessed 2026-10-04
10. Unlocator Support - How to bypass DNS hijacking - accessed 2026-10-04
11. Cloudflare Learning - What is DNS? - accessed 2026-10-04

Keep reading

Tools for this