This release fixes another bug (#1507 (comment)) in the dnscontrol check
subcommand related to the #1457 proposal. Thanks to @riku22 for reporting the bug!
Breaking changes:
- none
Major features:
- none
Provider-specific changes:
- none
Other changes and improvements:
- Fix #1507 (comment) BUG: With TYPE in creds.json, CAA compatibility check breaks (#1514)
Depreciation warnings
- Call for new volunteer maintainers for GCLOUD, NAMEDOTCOM, and SOFTLAYER. 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.
- ACME/Let's Encrypt support is frozen and will be removed after December 31, 2022. The
get-certs
command (renews certs via Let's Encrypt) has no maintainer. There are other projects that do a better job. If you don't use this feature, please do not start. If you do use this feature, please plan on migrating to something else. See discussion in #1400 - convertzone is frozen and will be removed after June 30, 2022. The
convertzone
stand-alone program is replaced by theget-zone
subcommand of DNSControl. It does everythingconvertzone
did and more. - Provider ACTIVEDIRECTORY_PS is frozen and will be removed after June 30, 2022. It is replaced by MSDNS which is 100% feature compatible and works better. (We believe nobody uses it.)
- get-zones syntax changes in v3.16 Starting in v3.16, the command line arguments for
dnscontrol get-zones
changes. For backwards compatibility changeprovider
to-
. See documentation for details.