feat(dns): add DNS auto-provisioning via RFC 2136 dynamic updates#24
Draft
fobispo-tc wants to merge 1 commit into
Draft
feat(dns): add DNS auto-provisioning via RFC 2136 dynamic updates#24fobispo-tc wants to merge 1 commit into
fobispo-tc wants to merge 1 commit into
Conversation
5255520 to
61e83a5
Compare
Add port.DNSProvisioner interface and DDNS adapter for automatic DNS record management (TXT, TLSA, SVCB) using RFC 2136 with TSIG auth. When configured, registration issues certs, provisions DNS, and activates in a single call. Revoke auto-deletes records. Domain suffix config auto-qualifies short hostnames. SVCB records provide agent connectivity parameters per the DNS-AID proposal (RFC 9460). Includes the _ans-badge URL fix: badge records point to the TL badge endpoint when tl-client.public-base-url is configured. Signed-off-by: Francisco Obispo <fobispo@tucows.com> Signed-off-by: Francisco Obispo <fobispo@tucows.com>
61e83a5 to
807624e
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
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.
Summary
port.DNSProvisionerinterface for automatic DNS record creation/deletionVerifyDNS(auto-create before verify) andRevoke(best-effort cleanup)dns.provisionerconfig section — independent of thedns.typeverifier setting_ans-badgeURL fix from PR fix(domain): point _ans-badge DNS record URL at transparency log #23 (badge records now point to TL, not agent endpoint)Motivation
In org-level deployments where the RA controls the DNS zone, requiring operators to manually add
_ans,_ans-badge, and_443._tcpTLSA records between VerifyACME and VerifyDNS is unnecessary friction. This feature lets the RA provision them automatically via RFC 2136 dynamic DNS updates, collapsing the registration flow from 4 steps to 2.Configuration
When
dns.provisioneris absent or empty, behavior is unchanged (manual DNS).Design Decisions
DNSProvisionerinterface — not combined withDNSVerifier(ISP compliance, matches existing port pattern)dns.type: lookup+dns.provisioner.type: ddns)Files Changed
internal/port/dns.goDNSProvisionerinterfaceinternal/adapter/dns/ddns.gointernal/adapter/dns/ddns_test.gointernal/adapter/dns/noop_provisioner.gointernal/config/config.goPublicBaseURLinternal/domain/dnsrecords.gotlPublicBaseURLparam for badge URL fixinternal/domain/dnsrecords_test.gointernal/ra/service/registration.godnsProvisionerfield + builderinternal/ra/service/lifecycle.gointernal/ra/handler/*.gocmd/ans-ra/main.goconfig/ra-{local,docker}.yamlTest plan
go test ./...)go build ./...)