0

hostname to blocklist lookup tool

Any chance of making a web tool in the support area where a user could enter a fqdn or domain name and see list of every blocklists (or security list) where the entry appears?   

Yes, the logs can be used, but it seems many community support questions ask something like why can't I access foo.example.com, and a typical reply is "check the logs"

Having a web tool could help anyone providing support to users that don't fully understand how to use the logs.

4 replies

null
    • Hey
    • 3 yrs ago
    • Reported - view

    It wouldn't solve much in my opinion, NextDNS isn't a tool thats On/Off it's customizable, so for that to happen, the user would have to know which filters they are using and for a new user knowing what the filters do and what to enable is a larger problem then going onto their logs and checking why it's blocked there.

    There is also already a way to see why something is blocked directly on your decice. Enabling Blockpages show the domain and every single filter that blocked it so it works even with multiple filters. Although it's up to them to decide, it wouldn't honestly resolve much since the user wouldn't see if it's blocked or not but the filters that block them leading to further confusion about what they are in the first place.

      • Calvin_Hobbes
      • 3 yrs ago
      • Reported - view

      Hey I understand what you're saying.  For people like you and I who understand how things are working it wouldn't be useful.  We know how to look at logs and solve problems.

       

       I was thinking it would help anyone in a support roll (helping a friend or a community post) when someone says "blah.example.com" doesn't work and see if it's caused by a Threat Intellegent feed or native tracker or an overly aggressive block list.

      The custom block page is fine for web surfing.   But when some other thing doesn't work (for example an app or game) doesn't work, the block page isn't seen by the user.

      Also, people won't ask support when the normal ads or trackers are blocked....that's why we use NextDNS.   For false positives where perhaps one of the more advanced features breaks something, it could be useful.

      Or maybe not.   I put it up for a feature request.   If I had the skill, I'd build it myself.   It might even be fun project for someone and could probably be done outside of NextDNS.  All the block lists are public.

      • Hey
      • 3 yrs ago
      • Reported - view

      It can be useful if implemented by NextDNS as a better logging option, with built in troubleshooting tools, so you can see that you should turn your WIFI Off/On on mobile or clear the DNS cache on PC, then it can start a temporary log that starts logging when the user presses the assumed button and opens the Troubled app, it would be a de-cluttered easier way of doing it and it wouldn't add any of the confusion or just a site that shows what filters block what. In terms of that, I think it would save time even for people that know their way around.

      • Hey
      • 3 yrs ago
      • Reported - view

      If they add filter false positive rates in the mix and explain that the higher the score the less troubleshooting needed, it would also give insight into the end user about what filters they should use. So a score of 1-5 for Security / Update Speed / False positive rate could be useful.

      So while using OISD I'd get 4.5 security 4.5 Updates and 5 False positive rate. 

      1HostPro would show 5 for security and updates but let's say 3.5 for false positives etc. 

      NextDNS filter shows let's say 4.5, 4.5, 4.5 as a great balanced filter etc. 

      They could also show the difference between filters for DNS and general filters since Adguard Base is more likely to give you issues compared to DNS since it's made for add-ons and other tools that filter the entire traffic.

Login to reply

Content aside

  • 3 yrs agoLast active
  • 4Replies
  • 67Views
  • 2 Following