Leverage NextDNS BlockList Metadata

jeffvogelsang

Hi all,

I'm curious if there's a way to, or interest in, leveraging the work NextDNS is doing to curate blocklists.

They are publishing their blocklist data on Github here: https://github.com/nextdns/metadata

A typical blocklist (Steve-Black's) is here:

https://github.com/nextdns/metadata/blob/master/privacy/blocklists/steven-black.json

The JSON format is simple:

{
  "name": "Name",
  "website": "URL to site",
  "description": "Description",
  "source": "URL to blocklist"
}

They also have bundles of blocklists. An example, their recommended default, is here:

https://github.com/nextdns/metadata/blob/master/privacy/blocklists/nextdns-recommended.json

The bundle JSON format is also simple:

{
  "name": "Name",
  "description": "Description",
  "sources": "[Array of URLs to blocklist sources]"
  ],
  "exclusions": [
    "[Array of domain strings to exclude]"
  ]
}

Bundles would be a great analog to the current feed groups.

I don't think you can point to and load these JSON configs in the Feeds or Groups interface for PFBlockerNG as they aren't understood?

Could be nice to expose the individual NextDNS block lists and bundles in the PFBlockerNG DNSBL feeds interface as configuration options, especially if NextDNS continues to curate these over time.

-J

BBcan177

@jeffvogelsang

The pfBlockerNG-devel package has an existing Feeds tab. It would probably be more efficient to request changes to the feeds or submit a PR against the database here:

https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/www/pfblockerng/pfblockerng_feeds.json

Keep in mind that I typically do not add feeds that are compilations of other Original Feeds. Best to go directly to the source. There are changes to be made to the json already as some feeds are now discontinued. That will happen in the next release.