What Shah says NextDNS does better
Shah's argument is simple. Cloudflare's resolver is fast, free and private, but it gives you no dashboard. NextDNS adds a live Logs tab. You can filter it by device and see timestamps and whether each query was blocked or allowed. A three-dot menu on each entry lets you block or allow that domain.
He also points to these features:
- Profiles. Each profile has its own blocklists, allowlists, security filters and logging. He runs three, and you can make as many as you like.
- Category blocking. You can block categories such as gambling, social media, dating apps and parked domains.
- Native tracking protection. These are ready-made lists aimed at telemetry from device makers. Windows, Apple, Samsung, Amazon Alexa and Roku are among them.
- CSV export. He suggests feeding the export to an AI model for analysis.
- Price. He puts the free tier at 300,000 queries a month, and the paid plan at $2 a month or $20 a year.
Device names aren't automatic
The most important caveat is that the dashboard only labels devices that identify themselves. NextDNS's help documentation says that, by default, logs only expose the public IP used to reach NextDNS. The result is that logs get less useful when many devices share one profile. Hmm, that is the exact situation most households are in.
NextDNS documents several ways to pass a device name:
- DNS-over-TLS. You prepend the name to the hostname, and the name may only use letters, digits and hyphens. A double hyphen stands in for a space, so "John Router" becomes
John--Router-abc123.dns.nextdns.io. - DNS-over-HTTPS. You append a URL-encoded name to the path, for example
[url]https://dns.nextdns.io/abc123/John's%20Firefox[/url]. - Query-string parameters. These can also carry a device ID, name, model and private LAN IP. NextDNS recommends this route.
- HTTP headers. These are recommended when many devices are tunnelled through one DoH connection, such as a DNS proxy on a router.
If you skip all of this, the log may show devices as unidentified. One NextDNS community user on the CLI client reported seeing "Unidentified device" until they turned on client-info reporting.
Windows specifics
Windows has a few options. Here is what the evidence supports:
- NextDNS Windows app. Setup guides describe pasting your configuration ID into the app's settings, then enabling it. One third-party guide says to enable "Send Device Name" there.
- MSI deployment. NextDNS's mass-deployment guide lists a
REPORT_DEVICE_NAMEproperty. It reports the device name and model with DNS queries so they appear in logs and analytics. A NextDNS staff reply in the same thread says the latest revision has it on by default. - Reliability. A user in that thread said the name still didn't report on a fresh Windows 11 machine. Verify it in the dashboard rather than assuming it worked.
- Native Windows 11 DoH. A forum answer points to the "Identify your devices" section at the bottom of the dashboard's Setup tab. A third-party guide notes that Windows 10 has no built-in DoH setting, so the app is the practical route there.
Cloudflare isn't a blank slate
"Cloudflare has no logs" is shorthand, and it isn't quite right. Cloudflare's own documentation says it retains only limited transaction and debug log data and deletes it within 25 hours. Its published commitments also say source IPs are truncated and deleted within 25 hours, and that the data isn't sold or used for ads. The difference is who can see the logs. Cloudflare's are for its own operation, while NextDNS's are a feature meant for the account holder.
The comparison also skips Cloudflare's filtered options. The 1.1.1.1 for Families resolvers block malware and phishing on 1.1.1.2 and 1.0.0.2. They add adult-content blocking on 1.1.1.3 and 1.0.0.3. Plain 1.1.1.1 doesn't filter. The family options have no per-device dashboard, but "Cloudflare can't block anything" isn't accurate.
Logging is a privacy choice
A DNS log is a list of the sites and services your devices contact. NextDNS lets you control this:
- Log domains and client IPs. These are optional settings. The CSV's
domaincolumn only appears if "Log domains" is checked, and the client IP column depends on "Log clients IPs". - Retention and storage. NextDNS's privacy policy, quoted in a community thread, says you can choose retention time and storage location, or turn logs off. It also says no logs are kept without an account.
- Export. The Settings tab has a "Download logs" button that produces one CSV file. The columns include timestamp, query type, protocol, status, the reasons a query was blocked or allowed, and device ID, name and model. That file is sensitive, so think twice before uploading it to an AI service.
One MakeUseOf setup guide advises non-developers to keep logging off. That fits the trade-off: the visibility Shah likes is the same data you may not want stored.
Telemetry blocking has limits
NextDNS's Windows list can cut some background traffic. A third-party setup guide says it covered eight vendors on 26 October 2026: Windows, Apple, Samsung, Xiaomi, Huawei, Alexa, Roku and Sonos. DNS filtering only affects lookups, though. It won't stop traffic that goes straight to an IP address or uses a different DNS path. Blocking a domain can also break a feature. That guide suggests adding one vendor at a time and checking the logs if something stops working.
Pricing: the dollar figures check out
The free tier's 300,000 monthly queries matches NextDNS's pricing page. The Pro plan there is $1.99 a month or $19.90 a year, and the page says prices are in USD, which fits Shah's rounded figures. NextDNS says that past the free quota it keeps answering DNS queries like a classic non-blocking service. Another guide says it then does no filtering and no logging until the month ends, and that NextDNS emails you at 250,000 and 300,000 queries.
Pricing pages change, so check the live page before subscribing.
Is it worth switching?
It suits you if:
- You want to know which PC, phone or TV is generating noisy lookups.
- You want different filtering rules for different household or small-office devices.
- You're willing to name each device and verify it in the dashboard.
Stick with Cloudflare if:
- You want one setting you never touch again.
- You don't want a stored lookup history at all.
- You only need basic malware filtering, which 1.1.1.2 provides.
To try NextDNS, create a profile and decide on logging and retention first. Then configure one Windows PC with a device name. Browse for a minute, and check that the right device shows up in the Logs tab before rolling it out wider.
The article is one writer's experience and reads like an enthusiast's endorsement. The documentation backs the core idea, but it also shows the device labels depend on your setup. DNS filtering is a useful layer, and it doesn't replace endpoint security.
References
- I ditched Cloudflare 1.1.1.1, and its replacement shows me what’s happening on every device MakeUseOf · 2026-11-18T13:00:17+00:00
- 1.1.1.1 Public DNS Resolver · Cloudflare 1.1.1.1 docs developers.cloudflare.com
- Device Information Log Enrichment - How-To Guides - NextDNS Help Center help.nextdns.io