Guide › Components

DNSBL

How DNSBL evaluates domain feeds in Unbound, chooses a response, resolves exceptions, and reports blocked queries.

DNSBL evaluates names inside the pfSense Unbound DNS Resolver. It does not install a browser extension or filter content after a connection is established; it decides the DNS response for a matching query.

Processing path#

  1. Download enabled DNSBL sources and read operator entries.
  2. Parse plain domains, hosts-style rows, and supported Adblock Plus/EasyList rules per line.
  3. Normalize names and reconcile block and allow rules by priority.
  4. Build a new DNSBL data set and swap it into the running resolver without restarting Unbound.
  5. Log matches according to the selected response mode.
DNSBL settings page with wildcard, HSTS, IDN and regex options
DNSBL settings.

Response modes#

ModeResolver responseLogging
DNSBL WebServer/VIPDNSBL sinkhole virtual addressYes; supports the block page path
Null Blocking0.0.0.0Selectable with or without logging
NXDOMAINName does not existSelectable with or without logging

A global logging/blocking mode on the DNSBL page overrides per-group response choices.

Feed and operator precedence#

DNSBL uses six priority bands. Higher bands win when rules for the same name conflict:

PriorityRule
1Downloaded feed block
2Downloaded feed allow (@@ or a Permit source)
3Downloaded feed block with $important
4Downloaded feed allow with $important
5Operator block, custom-list block, or operator regex
6Operator whitelist, TOP1M allow, or temporary operator unlock

$badfilter cancels the matching ABP rule in the same rule stream. This ordering keeps feed exceptions useful while preserving operator control.

ABP and EasyList#

Supported feeds can mix plain entries and ABP/EasyList syntax. Rule parsing is per line, so a feed does not need to be classified wholly as one format. Supported semantics include domain anchors, @@ exceptions, regular-expression rules, $important, and $badfilter.

Pre-defined DNSBL feeds grouped into ADs, Malicious and Phishing
Pre-defined DNSBL feeds grouped by purpose.

Complex feed and user regex is guarded at load and runtime. Avoid adding broad custom regex when a plain domain or wildcard entry expresses the same policy.

Sinkhole virtual address#

The package can own the DNSBL sinkhole VIP automatically. Confirm its IPv4 and IPv6 addresses do not overlap an interface, routed network, VPN, or another VIP. The VIP is only relevant to the WebServer/VIP response mode.

Client path#

DNSBL sees queries that reach pfSense Unbound. A client using an external resolver, DNS over HTTPS, DNS over TLS, a VPN-provided resolver, or a local hosts file may not use that path. pfBlockerNG includes controls that can assist with known encrypted-DNS endpoints, but network policy must deliberately force or permit client DNS behavior.

False positives#

  1. Find the event in Reports and confirm the feed/group.
  2. Decide whether the exception is temporary or permanent.
  3. Add a precise whitelist or use the report action.
  4. Reload DNSBL and confirm the name resolves.
  5. Report the false positive to the feed maintainer when appropriate.

An operator whitelist has the highest priority, including over $important feed blocks.

Top