Skip to content

AXFRDDNS: support unix domain sockets in update-mode/transfer-mode#4304

Open
tomfitzhenry wants to merge 1 commit into
DNSControl:mainfrom
tomfitzhenry:axfrddns-unix-domain-socket
Open

AXFRDDNS: support unix domain sockets in update-mode/transfer-mode#4304
tomfitzhenry wants to merge 1 commit into
DNSControl:mainfrom
tomfitzhenry:axfrddns-unix-domain-socket

Conversation

@tomfitzhenry
Copy link
Copy Markdown
Contributor

@tomfitzhenry tomfitzhenry commented May 18, 2026

My usecase is doing AXFR/DDNS via DNS-over-TLS with PKCS11, and to a server that has a self-signed cert whose pubkey pin I want to verify. This could plausibly be natively added to dnscontrol, but it would be a fiddly amount of config in the AXFRDDNS provider.

Unix domain sockets allow connecting via another program, that already exposes lots of the above configuration (stunnel/ghostunnel).

Why not just have that other program listen on a localhost port? That's then exposed to all processes on the host. Unix domain sockets are restricted by file ACLs.

Unix domain sockets allow connecting via another program.

Why not just have that other program listen on a localhost port? That's then exposed to all processes on the host.
Copy link
Copy Markdown
Collaborator

@TomOnTime TomOnTime left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Would you please also add a call to providers.RegisterCredsMetadata()?

This is a new feature, which is covered in Step 4 of https://docs.dnscontrol.org/developer-info/writing-providers

You can see an example in #4297

Thanks!

P.S. If you wish to do that in a separate PR, please let me know and I'll approve this as-is.

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

Development

Successfully merging this pull request may close these issues.

2 participants