opnsense / opnsense/plugins

dns/bind: add validate-except config option for split dns on forward zones

Open
#5,549 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
1.2k
Forks
863
Avg merge
2d 6h
Merged PRs (30d)
10

Description

Is your feature request related to a problem? Please describe.
When running a split-horizon DNS setup where the public domain is DNSSEC-signed, internal clients experience SERVFAIL errors when querying internal, unsigned forward zones. While BIND implicitly trusts local primary zones and bypasses validation for them, forwarded zones trigger strict recursive checks. BIND attempts to validate the forwarded zone against the public chain of trust and naturally fails.

Currently, the BIND plugin UI does not expose the validate-except directive, making it impossible to exclude these internal zones/subdomains from DNSSEC validation without manual backend workarounds that get overwritten by the template engine.

Describe the solution you'd like
Add a config option to the plugins general configuration page. I'll file a PR on the change.

Describe alternatives you've considered
None.

Additional context
None.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the BIND plugin's general configuration page and the template handling that generates its configuration. Trace how existing DNS options reach the generated configuration, then verify that a configurable validate-except option is exposed and supports internal forward zones without being overwritten.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.