What DNSControl/dnscontrol shipped
Written by FoxPlug from public releases; not affiliated with Dnscontrol. An automatic summary of the public release, pull request and commit data of github.com/DNSControl/dnscontrol. Dnscontrol did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- DNSControl v5.2.0 released with contributions from the community. Release
- Mittwald mStudio added as a new DNS provider using the official Go client. Pull request #4933
- Spaceship added as both a registrar and DNS provider. Pull request #4921
- OpenProvider added as a new DNS service provider supporting A, AAAA, CAA, CNAME, MX, SPF, SRV, TLSA, and TXT records. Pull request #4891
- M365_BUILDER rewritten in Go with updated records to match Microsoft's current requirements. Pull request #4936
- AZURE_PRIVATE_DNS provider now supports the same authentication methods as AZURE_DNS including OIDC. Pull request #4929
- OpenProvider provider improved with retry logic and exponential backoff for transient API failures. Pull request #4937
- CNAME target values are now lowercased during normalization. Pull request #4940
- Fixed a JSON injection security vulnerability in get-zone --format js output. Pull request #4928
- Integration tests now run on scheduled CI runs instead of being skipped. Pull request #4935
Why it matters
This release adds three new providers (Mittwald, Spaceship, and OpenProvider) expanding DNS management options. Existing Azure and M365 providers received significant improvements with better authentication support and updated configurations. Security and reliability fixes address a JSON injection vulnerability and transient API failures.
Changelog entry
- NEW PROVIDER: Mittwald mStudio DNS provider Pull request #4933
- NEW PROVIDER: Spaceship registrar and DNS provider Pull request #4921
- NEW PROVIDER: OpenProvider DNS service provider with support for A, AAAA, CAA, CNAME, MX, SPF, SRV, TLSA, TXT records Pull request #4891
- AZURE_PRIVATE_DNS: Added OIDC support and same authentication methods as AZURE_DNS Pull request #4929
- M365_BUILDER: Rewritten in Go with updated records to Microsoft's current requirements Pull request #4936
- OPENPROVIDER: Added retry logic with exponential backoff for transient API failures Pull request #4937
- Fixed: CNAME target rdata now lowercased in normalization Pull request #4940
- Fixed: JSON injection vulnerability in get-zone --format js Pull request #4928
- Fixed: Integration tests now run on scheduled CI runs Pull request #4935
- Improved: Test length adjusted per provider Pull request #4939
- Improved: Providers can declare record identity for duplicate checks Pull request #4883
- Documentation: Rewrote golden file documentation Pull request #4912
- Documentation: Fixed table of contents links to resolve on GitBook Pull request #4932
DNSControl v5.2.0 is out! New providers: Mittwald, Spaceship, OpenProvider. Improved Azure and M365 support. Security and reliability fixes. Thanks to all contributors!
DNSControl v5.2.0 released! This version adds three new DNS providers—Mittwald mStudio, Spaceship, and OpenProvider—while strengthening existing integrations. Azure Private DNS now supports OIDC authentication, and M365_BUILDER has been rewritten in Go with updated record requirements. Security improvements include a JSON injection vulnerability fix. Thanks to our community contributors!
Week of September 14, 2026
What shipped
- v5.1.0 released as the first production-ready release after v5.0.0. Release
- SCALEWAY provider fixed for TXT round-trip handling, SVCB parameters, SSHFP case sensitivity, NS TTL, and PTR support. Pull request #4919
- GCORE provider fixed to parse API names without trailing dots. Pull request #4923
- SVCB keys without values like no-default-alpn now handled correctly. Pull request #4909
- INWX sandbox question in dnscontrol init changed from confusing free text to yes/no prompt. Pull request #4882
- AUTODNS provider fixed to send bare FQDN as MX value instead of full RDATA. Pull request #4880
- AUTODNS provider fixed to clear legacy zone-level main record on update. Pull request #4881
- TENCENTDNS provider now matches package grades case-insensitively. Pull request #4884
- Documentation updated to point new users to dnscontrol init first. Pull request #4910
- Daily integration tests re-enabled. Pull request #4911
Why it matters
v5.1.0 brings multiple provider bug fixes discovered through integration testing, improving reliability for users of SCALEWAY, GCORE, AUTOWNS, TENCENTDNS, and other providers. Documentation improvements ensure new users get correct setup guidance and existing users find accurate reference information.
Changelog entry
- v5.1.0 released Release
- fix(p/SCALEWAY): correct TXT round-trip, SVCB params, SSHFP case, NS TTL, and PTR support Pull request #4919
- fix(p/GCORE): parse API names without a trailing dot Pull request #4923
- fix: SVCB keys that lack a value (no-default-alpn, others) not handled correctly Pull request #4909
- fix(p/INWX): ask the sandbox setting as a yes/no question in init Pull request #4882
- fix(p/AUTODNS): send bare FQDN as MX value, not full RDATA Pull request #4880
- fix(p/AUTODNS): clear the legacy "main" record on zone update Pull request #4881
- fix(p/TENCENTDNS): match package grades case-insensitively Pull request #4884
- fix(p/CNR): offer the debug mode levels as a list in init Pull request #4879
- docs: point new users to dnscontrol init first Pull request #4910
- ci: Re-enable daily integration tests Pull request #4911
DNSControl v5.1.0 is out. This release fixes five SCALEWAY provider issues, SVCB/HTTPS record handling, MX record bugs in AUTOWNS and TENCENTDNS, plus improved init prompts and docs.
DNSControl v5.1.0 is now available for production use. This release addresses multiple provider bugs discovered through integration testing: SCALEWAY round-trip fixes, SVCB key handling, AUTOWNS MX preference and TENCENTDNS package grade matching. Documentation improvements help new users get started with dnscontrol init, and integration tests are back online.