The Free Layer Your Kid Can't Click Past: OpenDNS Family Shield, Set Up and Verified
Your kid's tablet has a browser with settings you have locked down. It also has half a dozen apps that each open their own little web views, and none of them care about your browser settings. The only layer that sees everything a device talks to sits underneath all of it: the DNS server. This setup lives there, and it costs nothing for home use.
What DNS Filtering Actually Sees
Know exactly what the filter does first, because the marketing always blurs this line. Whenever any app wants to reach a website, it first asks your configured DNS server for the domain's IP address. A filtering DNS service like OpenDNS intercepts that one question. If the domain is on its block list — adult content, or known malware and phishing domains — it answers with a block page instead of an address.
What it does not see is what happens after the connection: it cannot read an encrypted page's contents, and it cannot stop anything that never goes through your DNS. Treat it as the floor, not the ceiling: cheap, invisible to casual use, and good at stopping broad categories. The rest is how to get it running on every device and prove it with commands instead of vibes.

Two Free Tiers, Four IP Addresses
OpenDNS runs two tiers that matter for a house, and both are free:
- Family Shield — no account, no app, no configuration beyond typing two IP addresses into your device or router. It blocks adult content plus the malware and phishing domains OpenDNS maintains. That fixed filter is the whole product, which is also its appeal: nothing to manage.
- Home User — a free account on OpenDNS. Same DNS-level blocking, but you choose the blocked categories and get per-device logs in the dashboard, so "what did this tablet visit" becomes a question with an answer.
The resolver addresses are the entire configuration; I verified both pairs respond as working resolvers before writing this:
Family Shield (no account): 208.67.222.123 and 208.67.220.123
Home User (free account): 208.67.222.222 and 208.67.220.220
For the account tier, sign up at login.opendns.com on the free Home User plan, not the paid one. The home internet security page has the current tier details if you want to read them first.
Put It on the Router, Not the Phone
The weakest place to set this up is a single device, because a kid who knows where the Wi-Fi settings are can find the DNS field too. The router is the choke point: every device on the network asks it for names, so one change covers the tablet, phone, laptop, smart TV and whatever you have not thought of yet.
The exact menu layout differs by router, but the path is always the same shape: log in to the router's admin page (the address is on a sticker on the unit), find the WAN or Internet settings — sometimes listed as "DNS servers" under connection settings — and replace the two DNS entries with the pair above. Save, reboot if it asks, done.
If your router hides those fields behind locked-down ISP firmware, use per-device setup below. The hybrid works: router for the house, device-level for the one tablet that keeps getting factory-reset by its owner.

Per-Device Setup, When You Can't Touch the Router
Windows: Settings > Network & internet > your active connection > IP settings > Edit, switch to Manual, enable "Set DNS server manually," enter the two addresses.
macOS: System Settings > Network > Wi-Fi (or Ethernet) > Details > DNS, remove the old entries and add the pair.
iOS / iPadOS: Settings > Wi-Fi > the info icon next to your network > Configure DNS > Manual, then add both addresses. This is the one for the kid's tablet.
Android: Wi-Fi settings > your network > IP settings > Static, then the DNS fields; newer builds may offer a "Private DNS" option instead, which changes the shape of the setup — check which one yours has first.
Prove It's Actually Working
Most setup guides skip this part; I would insist on it. A filter you cannot verify is just a hope.
First, confirm the resolver itself answers. From Windows:
nslookup example.com 208.67.222.123
From macOS or Linux:
dig @208.67.222.123 example.com +short
Either should return an address for example.com; a timeout means the DNS path is broken before you have even asked it to filter anything.
Second, confirm your device is actually using that resolver and not silently falling back to something else:
ipconfig /all
scutil --dns
Look for the 208.67 pair for your active adapter; if you see your ISP's addresses instead, the router change did not take.
Third, the behavioral test: a blocked domain returns OpenDNS's block page instead of the site. You don't need to hunt for an adult site — ask your kid to try something they already know is off-limits, or any domain you have confirmed sits on the block list. A block page where content used to load is the filter working.

What This Layer Won't Catch
Be honest with yourself about the gaps, because "I set up OpenDNS" is not "the problem is solved."
Some modern apps hard-code their own DNS-over-HTTPS traffic and bypass a plain DNS filter entirely. A kid who learns where the Wi-Fi settings live can point a device back at any resolver. And allowed domains are allowed wholesale: YouTube resolves fine, which means the in-site controls — Restricted Mode, a locked SafeSearch — still have to be on, because DNS filtering never looks inside a page.
So the setup that actually holds is layered: the router-level filter for everything, per-device settings for the devices that matter most, a standard non-admin Windows account so nothing gets installed without you knowing, and the platform-level restrictions inside the apps they actually use. Each layer covers the gaps in the others. None of them replaces the last one, which is a conversation — approachable, non-dramatic, "tell me what you found" instead of "why would you look for that."
The Bottom Line
Free, no subscription, no account required for the basic tier, and verifiable with two commands. That is rare enough to be worth doing properly: set it at the router, confirm the resolver answers, confirm the device is using it, and close the remaining gaps at the app level. Then you have spent an evening on a floor that holds, instead of money on a ceiling that does not.
Don't trust the download button. Trust the hash — and in this case, trust the nslookup output.
If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.