Feature Request: : Add allow-update-forwarding option for DDNS Updates with TSIG Key in BIND Web UI in os-bind
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Hello and many thanks for your work
I have multi-server DNS setups, secondary servers need to forward DDNS updates to the primary. Currently, this must be configured manually in the BIND config files like:
zone "intra" {
type secondary;
primaries { 172.12.33.4 key "DHCP_UPDATER"; };
file "/usr/local/etc/namedb/secondary/intra.db";
allow-update-forwarding { key "DHCP_UPDATER"; };
};
I'd like to request support for adding the allow-update-forwarding option for the seconarie zones to the os-bind plugin configuration in the OPNsense Web UI with allowing specification of forwarding rules, including the option to use TSIG keys for secure updates.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no files, tests, or entry points. Start by locating the os-bind configuration for secondary zones and existing TSIG-related settings; done means the Web UI can configure allow-update-forwarding rules, including TSIG keys, and produces the requested BIND configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100