0

Blocklist

I want to add my own custom blocklist. I am not able to find any option to add custom blocklist. If you do not allow then why you are getting paid for? Just to provide a DNS and your own blocklists? People can do this free with Adguard and also can create free DNS for LIFETIME. Lack of features is not an option for a paid service. There are better and free alternatives available.

8 replies

null
    • Thuan_Nguyen
    • 2 yrs ago
    • Reported - view

    I am also a paid user, and I urgently asked NextDNS department to give us the option to add our own filters.

    • rubcebgamnydwofTe5
    • 2 yrs ago
    • Reported - view

    If you have a suggestion for a blocklist, feel free to raise an issue on GitHub: https://github.com/nextdns/metadata/issues

    • Hey
    • 2 yrs ago
    • Reported - view

    Honestly I would also like this but it would be quite unreasonable to add this.

    The reason being, currently there is a set of filters that every server has, the listed filters we see. The users ID tells the server that it should use X-Y-Z filters for that user and any other allow/blacklist additions. It works and in a case of you changing location for load balancing or a problem would only require the new server to fetch the few blacklist/whitelists you have and you'd instantly be ready again. You wouldn't even feel this happen.

    The problem with having custom filters would be that, it's possible ofc but it would require additional space and power to make it work. It's only a few mbs right not huge, times that by a few thousand, that's a few gbs but let's say on centeral points with a ton of users it adds up, what if the users connected server switches, instead of instantly fetching the few filters you are talking about a lot of users constsntly changing adding and modifying their lists. Again it's possible but would require even more servers and even more powerful ones at that to work. 

    So they can just add more servers with addtional power to make this work right?

    It would affect the end user and for counties with lesser currencies and inflation that's even worse a dollar could be a genuine difference maker in the user affording it or not being able to spend that much. Again in the US a dollar is only a dollar but in other countries it can be worth far more but even in the US,if you don't want this but still have to pay more it doesn't make sense.

    So at the end, the required changes that they would have to do, it would make the service more expensive and give it a higher risk of failure with more stuff going on in general weather this be that the drives getting older with more use for updating the custom filters or just problems in general. 

      • Hey
      • 2 yrs ago
      • Reported - view

      I saw this after just posting it but it looks like a whole essay, probably should make it more friendly to look at next time.

      • Hey
      • 2 yrs ago
      • Reported - view

      Incase someone cares to read even more, server prices aren't cheap, I was looking around just to see after seeing a request on a thread and a server with 32 Cores Xeon and a 2x500gb ssd for redudency in a populated place could cost upwards of 6-11k depending on the service. Ontop of that with how NextDNS handles their servers by adding more capacity in cases like Facebook going off the grid that happened earlier this year, yeah it would definitely impact the end pricing.

    • Techno
    • 2 yrs ago
    • Reported - view

    I think at the very least the available blacklists should be updated. There's lists in there that haven't updated for well over a year. For a paid service this should be taken care of...

      • rubcebgamnydwofTe5
      • 2 yrs ago
      • Reported - view

      Techno If the blocklist they're providing hasn't been updated, there's nothing to change. Keep that in mind.

       

      Are you talking about a specific list that has had a recent update that doesn't line up with the NextDNS blocklist update time?

      • Hey
      • 2 yrs ago
      • Reported - view

      Techno As Justin said it's upto the provider to update them, the only filter that NextDNS manages is the NextDNS Ads & Tracking filter everything else is a direct link to the providers GitHub so when AdGuard or OISD for example updates it fetches it from their GitHub page. The ones that aren't updated are probably dead projects and you're right on that they shouldn't be there if they aren't getting updated anymore but it's for NextDNS to decide if they want to remove it or not and currently just ignore the seemingly dead ones. 

Content aside

  • 2 yrs agoLast active
  • 8Replies
  • 140Views
  • 6 Following