filter

filter

filter - provides domain blocking functionality

Description

The filter plugin is used to block domain name resolution, simliar to Pi-hole®.

Syntax

filter {
    ACTION TYPE DATA
}

• ACTION: [ allow | block ] What action to take
• TYPE: [ domain | regex | wildcard ] What type of DATA
• DATA:
  • domain: A raw domain to match. Subdomains are not matched
  • regex: A Go-formatted Regular Expression
  • wildcard: Common wildcard formats
    • Bare: example.com
    • Generic: *.example.com
    • Adblock Plus: ||example.com^
    • DNSMasq Address: address=/example.com/#

filter {
    ACTION list TYPE DATA
}

• ACTION: [ allow | block ] What action to take
• DATA: Lists of the following data types
  • domain: A raw domain to match. Subdomains are not matched
  • hosts: A hostsfile formatted list
  • regex: A Go-formatted Regular Expression
  • wildcard: Common wildcard formats
    • Bare: example.com
    • Generic: *.example.com
    • Adblock Plus: ||example.com^
    • DNSMasq Address: address=/example.com/#
• DATA: A [ file | http | https ] URL. Must contain only the TYPE specified.

filter {
    response TYPE [ DATA ]
}

• TYPE [ address | nodata | null | nxdomain ] Record type that should be the response to blocked domains
  • address: Only A and AAAA records are accepted, and only one of each. Lowercase record types are accepted.
  • nodata: Returns success code but no records
  • null (DEFAULT): Returns unspecified address records A 0.0.0.0 and AAAA ::
  • nxdomain: Returns an SOA record for the requested domain.
• DATA Only used for address responses

filter {
    update DURATION
}

• DURATION (DEFAULT=24h): any value accepted by time.ParseDuration

filter {
    listresolver RESOLVER [ SERVER_NAME ]
}

• RESOLVER: a resolver IP address to use when fetching remote lists. dns and tls schemes are accepted. Ports may be specified. IPv6 address are accepted when used with a scheme and port. Since listresolver is intended to be used when no other resolvers are available, only IP addresses are accepted.
• SERVER_NAME: Only used when resolver scheme is tls. Must be the host name of the resolver, otherwise resolving will fail due to being unable to verify the resolver's certificate.

Domain Matching

Values for regex directives are parsed directly by regexp.Compile, so if you're unfamiliar with Go regular expressions, verify them using https://regex101.com/?flavor=golang. Complex regular expressions should be loaded from a list instead of inline to avoid confusing the CoreDNS Corefile parser with symbols.

With how wildcard strings are cleaned and compiled, the following block wildcard directives are identical.

IMPORTANT: Allowed domains always take precedence. If a domain is in an allow list and a domain in that list is blocked explicitly or on block list, it will be allowed. Think of allow directives as force overrides and use them with caution.

filter {
    block wildcard example.com
    block wildcard *.example.com
    block wildcard .*.example.com
    block wildcard ||example.com^
    block wildcard address=/example.com/#
    block wildcard address=/example.com/0.0.0.0
}

AdblockPlus and DNSMasq formats are supported for flexibility and ease of migration from other solutions. Zone and Unbound configuration files are not supported.

Examples

# Use an aggregated block list, but allow `vortex.data.microsoft.com` for XBox
# Live achievements. Retrieve the block list using Quad9 over TLS. Respond to
# blocked domains with `A 0.0.0.0` and `AAAA ::` records. Update list every 24
# hours.

filter {
    listresolver tls://9.9.9.9 dns.quad9.net
    block list domain https://small.oisd.nl/
    allow domain vortex.data.microsoft.com
}

# Block all request except domains explicitly allowed in the list on the
# filesystem. Forward blocked requests to an internal web server to display a
# block page and log unapproved sites. Do not automatically update lists. Only a
# restart of CoreDNS will refresh the list's contents.

filter {
    block regex .*
    allow list domains file:///etc/coredns/whitelist
    response address A 10.0.1.50 AAAA 2001:db8:abcd:0012::ffff:0a00:0132
    update 0
}

Building

Clone the coredns repository and change into it's directory.

git clone https://github.com/coredns/coredns.git

cd coredns

Fetch the plugin and add it to coredns's go.mod file:

go get -u github.com/wranders/coredns-filter

Update plugin.cfg in the root of the directory. The filter declaration should be inserted before cache so that updates to the filter are applied immediately.

# Using sed
sed -i '/^cache:cache/i filter:github.com/wranders/coredns-filter' plugin.cfg

# Using Powershell
(Get-Content plugin.cfg).`
Replace("cache:cache", "filter:github.com/wranders/coredns-filter`ncache:cache") | `
Set-Content -Path plugin.cfg

Build using make:

make

Or if make is not available, simply run:

go generate && go build

The coredns binary will be in the root of the project directory, unless otherwise specified by the -o flag.

Container

A pre-built Container with this plugin is provided at the following locations:

ghcr.io/wranders/coredns-filter:latest

quay.io/wranders/coredns-filter:latest

CPU architectures include armv6 and armv7 (Raspberry Pi), aarch64, and x86_64.

The coredns binary is located at the root of the filesystem, so a Corefile mounted to /Corefile will be automatically detected without futher configuration.

Ports 53/udp (DNS), 443 (DNS-over-HTTPS), and 853 (DNS-over-TLS) are exposed by default.

[docker/podman] run -d -v ./Corefile:/Corefile -p 53:53/udp \
    ghcr.io/wranders/coredns-filter:latest

License

This plugin is licensed under the MIT license. See LICENSE for more information.