dns/ddclient: add bunny.net DNS provider - #5609
Open
teoulas wants to merge 1 commit into
Open
Conversation
teoulas
force-pushed
the
dns/ddclient-bunny
branch
from
August 6, 2026 17:54
1b15202 to
30e676e
Compare
teoulas
force-pushed
the
dns/ddclient-bunny
branch
from
August 6, 2026 18:03
30e676e to
cdd9458
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have read the contributing guidelines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
I opened an issue first for non-trivial changes and linked it below.
AI tools were used to create at least part of the code submitted herewith.
Model used: OpenAI GPT-5.6 Sol (
gpt-5.6-sol) via piExtent of AI involvement: AI assistance was used to inspect existing provider patterns and the official bunny.net OpenAPI specification, draft the provider and UI changes, and create mocked verification steps. I manually queried the live bunny.net API, reviewed the implementation, deployed it to OPNsense, and verified that it successfully updated an actual DNS record.
Describe the problem
As mentioned in the linked issue - you can't update DNS records with the existing "custom" service. Bunny.net API requires passing the API key in a request header and the IP in the JSON request body.
Describe the proposed solution
Re-use the existing form fields:
Use the API to discover the zone id and existing records. Update the records matching the ones configured in the UI.
API doc: https://core-api-public-docs.b-cdn.net/docs/v3/public.json
Related issue
#5608
Screenshots
(ignore the red validation error - I initially forgot to set the interface 🙃 )