-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
feat(adguardhome): Add AdGuard Home provider #3520
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: gabe565 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @gabe565! |
Oops, somehow I missed #3367 before now. I'll leave this open for now since my implementation:
Feel free to let me know if I should close this. |
2aa31db
to
8f69606
Compare
8f69606
to
8d0c812
Compare
8d0c812
to
1212386
Compare
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@mloiseleur: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description
This PR adds an AdGuard Home provider, which manages DNS rewrite entries for AdGuard Home.
The provider uses AdGuard Home's JSON API to create/delete records. AdGuard Home only supports A/AAAA/CNAME DNS rewrites, so ownership is not supported (similarly to the PiHole provider).
Fixes #3243
Checklist
Example DNS Rewrites