DNSControl 5.7.1

What's new in 5.7.1

Greetings DNS fans!
Thanks to all contributors involved in this release! This is a community project and we couldn't do it without all of your contributions!
Sincerely,
--Tom Limoncelli
Monthly video call!
Everyone is invited to the Monthly DNSControl Community Video Conference Call on the 2nd Tuesday of each month. Join whether you are a new user with questions or an experienced developer that wants to discuss DNSControl internals... or anything in between! Meeting details on
GitHub Discussions.
Experimental: Try the new D() syntax!
Select credential entries directly with REGISTRAR() and SERVICE() in dnsconfig.js. The legacy syntax remains supported; this revision replaces the experimental PROVIDER()/DNS_SERVICE() syntax from v5.3.0. See the examples in the conversion guide. Please test it and share feedback!
Changelog
Provider-specific changes:
- 2155390b054f3a6ef5ada60b47d148e6337592e5: fix(p/BIND): bug: Writing zonefile mangles "repeated zone" labels (#5037) (@spicysharkco)
- ee93a5550a3d16e3be5a32c9e65154c4cc0da43a: fix(p/NAMECHEAP): stop corrupting TXT records longer than 255 bytes (#5036) (@louneskmt)
- 329c40e606c239dc1748d3b3553538fa0eb774c3: fix(p/AZURE_DNS): bug: intermittent "resource type does not match the type in the request body" errors (#5040) (@TomOnTime)
Bug fixes:
- ec3d8013718ba1dbc838c096e2e51a2572204d7e: fix(D_EXTEND): ignore the empty tag when extending a subdomain (#5034) (@spicysharkco)
- f0e54a988d023e7853d10d457a85229f6859ccb4: fix(IGNORE): bug: .foo and .foo both act like .foo (.foo has no "stop" pattern) (#5038) (@spicysharkco)
- d0901a69c08831ff4907c5c3a0d232fbeb83f076: fix(LOC): preserve thousandths of arcseconds in coordinates (#5035) (@spicysharkco)
Deprecation warnings
Warning

• REV() will switch from RFC2317 to RFC4183 sometime after v5.0 is released. This is a breaking change. Warnings are output if your configuration is affected. See https://docs.dnscontrol.org/language-reference/top-level-functions/revcompat
• NAMEDOTCOM, OPENSRS and SOFTLAYER need maintainers! These providers have no maintainer. Maintainers respond to PRs and fix bugs in a timely manner, and try to stay on top of protocol changes.

Full release notes »