Alright, here's a clean and powerful feature request draft you can send to NextDNS support, post on their GitHub, or drop in their community
:
Feature Request: Advanced Filtering (Wildcard, JS-Based, and Pattern Matching)
Hello NextDNS team,
First off, thank you for building such a powerful and privacy-focused DNS filtering service. I'm a daily user and really appreciate the control NextDNS gives over tracking, ads, and content filtering. However, I’d love to request some features that would take the service to the next level, especially for power users:
1. Wildcard Domain Support
Instead of manually blocking every subdomain, allow us to use wildcards like:
*.ggpht.com
yt*.googleusercontent.com
This would simplify and strengthen domain-level filtering and save time when dealing with aggressive subdomain spamming.
2. Regex or Pattern-Based Domain Filtering
Support for domain rules using basic regex or pattern matching like:
/.*sponsor.*/
/yt[0-9]+\.ggpht\.com/
This would make filtering smarter, especially for domains that change structure frequently or are used for obfuscation.
3. JavaScript-Based Cosmetic Filtering (Advanced)
Inspired by uBlock Origin:
- Ability to define JS or CSS rules to hide sponsored content, banners, or dynamically inserted ads.
- For example: removing YouTube sponsor banners or other UI elements.
Even limited support would massively improve the experience for users who want more than just DNS-level blocking.
4. Optional “Content Type” Blocking
Let us block domains by type (e.g., image
, script
, font
, etc.) so users can fine-tune access. For example:
||yt3.ggpht.com^$image
This can be useful to allow YouTube functionality but block unwanted thumbnails or sponsorships.
Why It Matters
Content delivery and ad tech are getting more aggressive. Many sponsorships and tracking assets are being embedded in legitimate domains like googleusercontent.com
, yt3.ggpht.com
, or even CDN URLs. DNS filtering alone sometimes isn't enough—and manual blocklists can get bloated fast.
Adding these features would:
- Give users deeper control
- Reduce reliance on third-party blocklists
- Compete more directly with uBlock Origin-level customization for mobile and system-wide filtering
All this should implement, right from private DNS level, using smart AI.
Thanks again for the great service. Looking forward to your thoughts!
— [Flexy4]
Please looking forward to seeing this features in future updates
1 reply
-
This is a DNS service that cannot be used to filter website content, only domains. Points 3 and 4 are therefore not realisable. Point 1: Wildcards at the beginning of a domain are already possible, i.e. *.example.com to block example.com and all subdomains with one rule.
Content aside
- 12 days agoLast active
- 1Replies
- 72Views
-
3
Following