github StackExchange/dnscontrol v4.14.0

10 hours ago

Hello DNS Fans!

The big news is that the concurrent data gathering feature is stable and will become the default in the next release. Instead of new commands (ppreview/ppush) the functionality is enabled using the --cmode flag.

  • v4.14: --cmode defaults to legacy (old code, data gathering is done serially)
  • v4.15: --cmode defaults to concurrent (new code, data gathering is done concurrently)
  • v4.16: The legacy mode is removed

Any use of the old, legacy, code prints a warning:

WARN: In v4.15 --cmode will default to "concurrent". Please test and report any bugs ASAP. 
In v4.16 or later, "legacy" will go away. See https://docs.dnscontrol.org/commands/preview-push

Any use of the ppreview/ppush commands prints a warning similar to:

WARN: ppreview is going away in v4.16 or later. Use "preview --cmode=concurrent" instead.

Other major changes/improvements:

  • --report now works in preview, not just push.
  • CLOUDNS now supports LOC and AutoDNSSEC.
  • The "# of corrections" count was wrong for some providers. It should now be accurate for all providers.

Thanks to everyone for their contributions! This is a community project and we couldn't do it without all your help!

Tom

Changelog

Major features:

Provider-specific changes:

Documentation:

CI/CD:

Dependencies:

Other changes and improvements:

Deprecation warnings

Warning

  • REV() will switch from RFC2317 to RFC4183 in v5.0. This is a breaking change. Warnings are output if your configuration is affected. No date has been announced for v5.0. See https://docs.dnscontrol.org/language-reference/top-level-functions/revcompat
  • MSDNS maintainer needed! Without a new volunteer, this DNS provider will lose support after April 2025. See #2878
  • NAMEDOTCOM 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.
  • get-certs/ACME support is frozen and will be removed without notice between now and July 2025. It has been unsupported since December 2022. If you don't use this feature, do not start. If you do use this feature, migrate ASAP. See discussion in issues/1400

Install

macOS and Linux

Install with Homebrew (recommended)
brew install dnscontrol
Using with Docker

You can use the Docker image from Docker hub or GitHub Container Registry.

docker run --rm -it -v "$(pwd):/dns" ghcr.io/stackexchange/dnscontrol preview

Anywhere else

Alternatively, you can install the latest binary (or the apt/rpm/deb/archlinux package) from this page.

Or, if you have Go installed, you can install the latest version of DNSControl with the following command:

go install github.com/StackExchange/dnscontrol/v4@main

Update

Update to the latest version depends on how you choose to install dnscontrol on your machine.

Update with Homebrew

brew upgrade dnscontrol

Alternatively, you can grab the latest binary (or the apt/rpm/deb package) from this page.

Don't miss a new dnscontrol release

NewReleases is sending notifications on new releases.