Skip to content
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.

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

dns/bind: enable DNSSEC zone signing #4258

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

Conversation

FeKn
Copy link

@FeKn FeKn commented Sep 27, 2024

Enables the configuration of 'dnssec-policy' and 'inline-signing' to primary zones for automatic DNSSEC signing.
The field 'DNSSEC policy' in the settings of primary zones allows the selection of the 'default' built-in policy or a 'custom' policy. This 'custom' 'dnssec-policy' can be configured within the 'General' tab (see example in help text).
Checking the 'DNSSEC inline-signing' checkbox in the primary zone settings enables 'inline-signing' (see help text).

Enables the configuration of 'dnssec-policy' and 'inline-signing' to primary zones for automatic DNSSEC signing.
The field 'DNSSEC policy' in the settings of primary zones allows the selection of the 'default' built-in policy or a 'custom' policy.
This 'custom' 'dnssec-policy' can be configured within the 'General' tab.
@FeKn
Copy link
Author

FeKn commented Oct 1, 2024

Some additional information:

The required DNSSEC keys are generated fully automatically by BIND after activation of the 'dnssec-policy' and stored by default in /usr/local/etc/namedb/working/. The location can be adjusted as required using key-directory.

The 'dnssec-policy' default generates a Combined Signing Key (CSK). Dedicated Zone Signing Keys (ZSK) and Key Signing Keys (KSK) can also be generated with the 'dnssec-policy' custom (see example in help text of the 'custom DNSSEC policy' field).

The zone is signed automatically by BIND each time the zone is changed.

The appropriate public CSK or KSK can then be added as a DS record in the superordinate DNS zone, so that the primary zone managed by OPNsense is classified as trusted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant