Skip to content

Fix Bogus DNSSEC Validation Domain in unbound.md #1252

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Fix Bogus DNSSEC Validation Domain in unbound.md #1252

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e2d02fc
Update unbound.md to fix DNSSEC validation domain error
HeliusMagnum Jun 12, 2025
a965a1c
Update unbound.md
HeliusMagnum Jun 12, 2025
419117c
Update unbound.md
HeliusMagnum Jun 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/guides/dns/unbound.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,11 +168,11 @@ The first query may be quite slow, but subsequent queries, also to other domains
You can test DNSSEC validation using

```bash
dig fail01.dnssec.works @127.0.0.1 -p 5335
dig dnssec.works @127.0.0.1 -p 5335
dig bogus.nlnetlabs.nl @127.0.0.1 -p 5335
dig +ad cloudflare.com @127.0.0.1 -p 5335
```

The first command should give a status report of `SERVFAIL` and no IP address. The second should give `NOERROR` plus an IP address.
The first command should give a status report of `SERVFAIL` and no IP address. The second should give `NOERROR` plus an IP address in addition to a `ad` in the `flags:` section. The `ad` signifies (Authentic Data), indicating the DNS response has been authenticated and validated using DNSSEC.

### Configure Pi-hole

Expand Down