DNS Blocking for Focus: A Calmer Internet for ADHD and Deep Work

Most advice about focus assumes the problem is you. Try harder. Want it more. Build better habits. For a lot of people, and especially for people with ADHD, that framing is not just unhelpful, it is the wrong diagnosis. The pull toward a feed or a video or a news refresh is not a character flaw. It is the intended outcome of products that are very good at being hard to put down. Asking willpower to win that contest, dozens of times a day, is asking it to do a job it was never built for.

This is a guide about moving the block to a place where willpower does not have to keep showing up: the DNS layer. It will not promise you a transformed brain. It will explain, concretely, why app-level blockers tend to leak, what resolver-level blocking actually does, and where its limits are.

Why willpower keeps losing

The honest version of the focus problem looks like this. Every time you reach for a distraction, a small negotiation happens. Part of you wants to keep working; part of you wants the quick hit of novelty. On a neurotypical day, with a rested brain, the working part wins often enough. On a tired day, a stressed day, or with an ADHD brain that already finds delay and effort harder to summon, the negotiation tilts the other way.

The trouble is that the negotiation never ends. You win it at 9:14, then you have to win it again at 9:16, and 9:31, and every time a notification or a stray thought reopens the question. Each individual "no" is small. The cumulative tax of saying no all day is enormous, and it draws from the same depleted account you need for the actual work.

The goal is not to win the argument more often. The goal is to stop having the argument.

Why app-level blockers leak

The common fix is an app-level blocker: an extension or an app that hides the distracting site. These help some people, and if one works for you, keep it. But they share a few structural weaknesses that an ADHD brain is especially good at finding.

• They are uninstallable in a moment of weakness. The block lives on the same device, behind the same settings you control while distracted. Removing it takes ten seconds, and ten seconds is not much friction when the reach is automatic.
• They are per-device and per-browser. You block the site in your work browser, then open it in a second browser, or on your phone, or in the app version. The hole is wherever you did not install the tool.
• They invite negotiation by design. Many show a "you have this blocked, continue anyway?" button. That button reopens the exact negotiation you were trying to retire.

None of this makes app-level blockers useless. It makes them leaky in precisely the situations where you most needed them to hold.

What changes at the DNS layer

DNS is the system that turns a domain name like example.com into an address your device can connect to. Before your browser loads anything, it asks a DNS resolver where a domain lives. If the resolver declines to answer for a domain you have chosen to block, the connection never starts. Nothing loads. There is no page to look at, and no "continue anyway" button waiting on it.

Guardino is a DNS resolver you configure once per profile, using encrypted DNS (DoH or DoT). Because the policy lives at the resolver rather than on the device, a few useful things follow.

• It applies across every device that uses the profile. Laptop, phone, tablet. The block does not care which browser or app you open. The request to a blocked domain fails the same way everywhere.
• The off switch is not one tap away. Turning a focus policy off means going to your dashboard and changing it deliberately, rather than dismissing a prompt mid-reach. That small distance is the entire point.
• A focus profile bundles the decision once. Instead of choosing "not now" for each site, each time, you decide once what a focused block of work should exclude, and the resolver enforces it until you say otherwise.

To be precise about what this is and is not: DNS sees domains, not the contents of pages. It can decline to resolve a distracting domain, but it does not read your messages or your documents. That is a privacy benefit, and it is also a real limit. DNS blocking is coarse. It works at the level of "this domain, yes or no," not "this part of this site." We will come back to that limit, because pretending it does not exist would be dishonest.

Setting up a focus profile

In Guardino, a focus profile is a policy you switch on for deep work. A reasonable starting point looks like this.

1. Create a dedicated profile for focus rather than editing your everyday one. You want to be able to switch back to normal browsing without unpicking individual rules.
2. Turn on Focus mode and the categories that pull at you most. The Social-media bundle is the usual culprit. Add the Mind Shield policy if attention-manipulation domains are part of your pattern. Keep it narrow at first.
3. Add a few custom deny rules for the specific sites that are your personal kryptonite, the ones a category might miss.
4. Add allow rules for anything you actually need during deep work, so the profile does not break a tool you depend on. Honesty with yourself here matters more than strictness.
5. Apply it to every device by configuring each one with the profile. On iOS that is a .mobileconfig; on Android, the QR code or Private DNS hostname. The walkthrough is at /setup.

The first version will be wrong in small ways. You will block something you needed, or miss something you did not. That is normal. Adjust it over a week rather than trying to get it perfect on day one.

Realistic expectations

Here is what this does and does not do, stated plainly.

DNS-level focus blocking removes the moment-of-reach friction across your devices and retires the all-day negotiation for a defined set of domains. For many people, that alone meaningfully changes how a working session feels. The distraction is not one tap away; it is one deliberate settings change away, and that gap is often enough.

What it does not do: it does not make the work itself easier, it does not address ADHD's effect on initiation or task-switching, and it cannot block a category of behavior cleanly when that behavior lives on a domain you also need. If your distraction is a site you genuinely use for work, DNS cannot tell a useful tab from a doom-scroll tab on the same domain. That is a real gap, not a bug to apologize away.

It also is not a replacement for the on-device tools you may already use. Apple Screen Time and Google Digital Wellbeing are good at time budgets, app limits, and schedules on a single device. Guardino enforces domain policy across all your devices at the network layer. These complement each other. Use them together: let Screen Time handle "thirty minutes of this app per day," and let the resolver handle "this domain does not load during deep work, on anything."

A gentler frame

If you have ADHD, you have probably been told to try harder more times than you can count, usually by people who did not understand what they were asking. The value of moving a block to the DNS layer is not that it makes you more disciplined. It is that it stops requiring discipline for one specific, exhausting decision, so the discipline you do have can go somewhere that matters.

A failed focus session is not a verdict on you. It is information: a domain to add, a rule to soften, a profile to adjust. The tool is meant to be edited, not obeyed. If you want to try it, you can start a free profile at /dashboard/register and read exactly how query data is handled at /legal/privacy. Keep the tools you already trust. Add this one where it helps. Then get back to the work you actually wanted to do.