Temporarily disable filtering
Before I migrated from Pi-hole, there was an option to disable blocking for 10 seconds, 30 seconds, 5 minutes, etc. I was able to use that for troubleshooting.
E.g. to identify if Pi-hole was causing a problem, uBO, or the website was having a problem. Pain having to change DNS to verify if a blocklist is causing it.
When something isn't working on my wife's computer, I have to go through log and start adding some things that could be a problem, wait for TTL, and see if that fixes it. World be great if we could have a disable button per profile so that it just acts as a resolver without any blocking (basically, same as if a free user goes over 300,000 queries in over month).
56 replies
-
It has been three years since I posted this and we haven’t received a single response from @nextdns (if that is valid), @Romain Cointepas, or @Olivier Poitrey.
I’m still a paying customer as I love the product, but this is obviously a desired feature.
-
3 years later and 240 upvotes. Still not implemented? I’ve been a subscriber for several years and often promote Nextdns and complain about the complainers, but seriously this is getting ridiculous.
It’s not just this particular idea. Several obvious and seemingly simple to implement requests are being ignored (cleaning up no longer maintained lists, for example).
Oddly, a few ideas/requests have been implemented without any indication of why they were chosen.
There’s competitive services (both local and hosted) that are evolving and perhaps surpassing what was once the clear leader in DNS filtering. My annual subscription just renewed and I’m going to look at other options before the next renewal period.
I don’t really want to start over with a different service or learn how to implement a locally hosted system, but I’m considering doing just that.
Come on @nextdns, show your customers some love. Please!
-
I too made an account just to suggest basically this idea (I was actually going to suggest individual switches for each block list to make isolating the problem even easier), but the fact that the OP is over 4 years old and this feature still isn't implemented is extremely disappointing. I wish I would have checked on this before paying for a year literally 3 days ago, but here's hoping I guess...
-
In addition to making troubleshooting easier by quickly ruling out DNS, it's often just easier to drop all filtering real quick for something that you already know is DNS, rather than add a rule. I ran into this today when trying to adjust email preferences (unsubscribe) for a company. The unsubscribe link routed me though a click tracker. Currently, even though I know the click tracker is the issue and what the URL is, I have to go into allow lists, add the click tracker, revisit the link to get to the unsubscribe, then go back into allow list and disable that rule. If there was a "pause for 30 seconds" button, I could one-click that and be done with it. That's enough time to get through to the unsubscribe address and my rules will automatically revert. It would be nice to either have a default like 30 second but allow for custom time ranges, or have several to pick from (e.g. 10 seconds, 30 seconds, 5 mins...)
Content aside
-
261
Likes
- 5 days agoLast active
- 56Replies
- 6872Views
-
62
Following