Release v1.12.0

Allow specifying block response in configuration

NXDOMAIN is the traditional response code for blocking DNS queries, but
can make it difficult to differentiate between actual DNS problems and
DNS blocklists. This change introduces the ability to respond with
REFUSED instead, to make it easier to identify DNS blocks.

The default behaviour remains to respond with NXDOMAIN, so no additional
configuration is required to maintain current behaviour.

Release v1.11.0

v1.11.0

Release v1.10.0

Run go mod tidy

Release v1.9.0

Bump github.com/prometheus/client_golang from 1.13.0 to 1.14.0

Bumps [github.com/prometheus/client_golang](https://github.com/prometheus/client_golang) from 1.13.0 to 1.14.0.
- [Release notes](https://github.com/prometheus/client_golang/releases)
- [Changelog](https://github.com/prometheus/client_golang/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prometheus/client_golang/compare/v1.13.0...v1.14.0)

---
updated-dependencies:
- dependency-name: github.com/prometheus/client_golang
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Release v1.8.0

Add support for allowlists

This introduces a new configuration parameter `allowlist` that takes
exactly one argument: a path to a list of domains that will never be
blocked by this plugin.

The behaviour of the allowlist is:

1. If a DNS RR should be both blocked and allowed, it will always be
   allowed, regardless of domain specificity. If `example.com` in the
   allowlist, and `foo.bar.baz.example.com` is in the blocklist, a
   query for `foo.bar.baz.example.com` will be allowed.

2. It introduces a distinct counter that is for domains that were not
   blocked because of your allowlist. These counters will only be
   incremented if the RR exists in both the blocklist and the allowlist,
   and will not be incremented if the RR only exists in the allowlist.

3. It's one allowlist per blocklist configuration block. If you have
   multiple allowlist sources, they must be merged into a single list
   before they can be used.

4. Child RRs of allowlist entries will be considered as being in the
   allowlist. If `example.com` is in the allowlist, `bar.example.com`
   is also treated as being in the allowlist.

Release v1.7.0

Add test to ensure child domains don't block parents

Release v1.6.1

What's Changed

• Bump github.com/coredns/caddy from 1.1.0 to 1.1.1 by @dependabot in #4
• Bump github.com/coredns/coredns from 1.8.1 to 1.9.3 by @dependabot in #2
• Bump github.com/stretchr/testify from 1.6.1 to 1.7.4 by @dependabot in #6

Full Changelog: v1.6.0...v1.6.1

Release v1.6.0

v1.6.0

Release v1.5.0

v1.5.0

Release v1.4.0

v1.4.0