Skip to content

Releases: StackExchange/dnscontrol

v4.15.2

17 Dec 14:48
@github-actions github-actions
v4.15.2
c74fbd5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.15.2 Latest
Latest

Happy holidays, DNSControl Fans!

Another quick bugfix release. This is particularly important if you use the BIND provider.

Bug: BIND

In 4.15.1 a bug was introduced that made the BIND provider use the
same filename for all zonefiles. That is fixed in this release. As a
bonus, BIND joins the list of providers that can run concurrently.

Do not use 4.15.1 if you use BIND.

Possible bug: IGNORE() plus MYTHICBEASTS

We're tracking a bug that was reported involving IGNORE() with MYTHICBEASTS (#3227). If you use any of the IGNORE*() functions, please push with caution.

It might affect other providers that use the diff2.ByZone() function call (AUTODNS, BIND, REALTIMEREGISTER, SAKURACLOUD) with a smaller change it will affect providers that use the diff2.ByRecordSet() function (AZURE, GCLOUD, GCORE, HUAWEICLOUD, NS1, POWERDNS, ROUTE53, TRANSIP).

If you use any of those providers, we can use your help! Please run the integration tests (https://docs.dnscontrol.org/developer-info/integration-tests) and report if they were successful or not. This release includes a new test that should trigger this bug: Integration test number 77 IGNORE w/change b3227

That's it!

Sorry for the releases right before most people are going on break! If you are concerned about other issues, the last v4.14.x release was very stable and is backwards compatible.

Best,

Tom

Changelog

Provider-specific changes:

Documentation:

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.

Contributors

cafferata and tlimoncelli
Assets 14

v4.15.1

13 Dec 14:45
@github-actions github-actions
v4.15.1
4357950
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.15.1

Hi DNSControl fans!

The speed and concurrency benefits announced in v4.15.0 were accidentally only applied to preview and not push. The 2-byte change in #3249 fixes that. Now push is as fast as preview (plus the time it takes to do any updates).

One user reported runtimes went from 57 seconds to 7 seconds. That's a 87% reduction in run-time!

Best,
Tom

Changelog

Documentation:

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.

Contributors

willpower232 and tlimoncelli
Assets 14
Loading

v4.15.0

13 Dec 01:50
@github-actions github-actions
v4.15.0
0b85cf2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.15.0

Greetings and happy holidays, DNSControl fans!

Santa (or the super-natural gift-delivery being of your choice) has graced us with THREE big, new, exciting, features, plus a ton of other fixes and improvements.

BIG NEWS # 1: The last line of a D() statement can now have a comma!

In the past, leaving off the last comma would give an error:

D("example.com", REG_NONE, DnsProvider(DSP_EXAMPLE),
    A("test", "1.2.3.4")              <<< look, Ma!  No comma!
END);

### version 4.14.x:
$ dnscontrol check
executing dnsconfig.js: (anonymous): Line 183:25 Unexpected token )

### version 4.15.0:
$ dnscontrol check
No errors.

Best of all we got this feature simply by upgrading to the newest version of the JavaScript interpreter we use (https://github.com/robertkrimen/otto). In the latest release @linuxerwang (who has probably never heard of our project) submitted this enhancement in robertkrimen/otto#520 and we all benefit.

This affects all kinds of JavaScript lists, not just D() statements.

Thanks, Santa! .... I mean @linuxerwang!

BIG NEWS # 2: The default for --cmode is now concurrent.

This means your preview will run many times faster because all the domains are collected concurrently. Some people have reported runtimes are reduced 50-75%.

This change was announced months ago in #3142 plus dnscontrol printed warnings since v4.14.0.

The following providers added concurrency support in this release: CLOUDNS, CNR, DIGITALOCEAN, GANDI_V5, HETZNER, NAMECHEAP, NETLIFY

Providers that already support concurrency include: AZURE_DNS, CLOUDFLAREAPI, CSCGLOBAL, DESEC, GCLOUD, NS1, ROUTE53, TRANSIP.

This code is a bit new. If you find a bug, use --cmode=none to disable concurrency. (and file a bug report!)

BIG NEWS # 3: Notifications can now be sent using Shouterr

Notifications are now handled by the Shouterr package. Shouterr supports every chat system I've heard of, plus plenty of other systems. In the future Shouterr will become the standard way to send notifications and other methods will be deprecated. How to set up notifications is documented at https://docs.dnscontrol.org/advanced-features/notifications.

Other new features worth mentioning:

  • NEW PROVIDER: CentralNic Reseller (CNR) - formerly RRPProxy (#3203) (@AsifNawaz-cnic)
  • PORKBUN: handles retries/ratelimits better, and now also supports CAA.
  • The get-zones subcommand is more reliable, which probably also makes preview more reliable.

Thanks to everyone for their contributions! This is a community-driven project and we couldn't do it without all your PRs, reviews, and other support!

Stay safe! See you in the new year!

--Tom

Here's the details:

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.

Contributors

willpower232, linuxerwang, and 6 other contributors
Assets 14
Loading

v4.14.3

07 Nov 23:47
@github-actions github-actions
v4.14.3
5c68ccb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.14.3

Hi DNSControl fans!

Another bugfix release that only affects very few users.

  • NS1 is in the process of removing support for URLFWD, which means our integration tests for that feature have started to fail. I've removed integration tests for URLFWD, but but the feature continues to exist in our code in case anyone still has access to the feature (#3195) (@tlimoncelli)
  • IMPORT_TRANSFORM (a feature only for use by Stack Overflow) now lets you skip individual records (#3193) (@tlimoncelli)
  • And of course, updated the dependences (#3197) (@tlimoncelli)

Changelog

Provider-specific changes:

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.

Contributors

tlimoncelli
Assets 14
Loading

v4.14.2

05 Nov 14:46
@github-actions github-actions
v4.14.2
8a6912b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.14.2

Greetings DNSControl Fans!

This is a bugfix release. The bug only affects one user of DNSControl (you know who you are) therefore adopting this release isn't urgent. This release also bumps modules for HUAWEICLOUD, ORACLE, and SOFTLAYER.

Changelog

CI/CD:

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.

Contributors

tlimoncelli and dependabot
Assets 14
Loading

v4.14.1

01 Nov 13:49
@github-actions github-actions
v4.14.1
a0f7123
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.14.1

Greetings DNSControl Fans!

This is a bugfix release, though one new feature is included (GCORE gains support for GeoDNS/Failover thanks to @xddxdd).

  • NS1 no longer fails if it sees a REDIRECT (#3167) (@kabenin)
  • ORACLE no longer gives invalid warnings in one situation (#3178) (@fabienmazieres)
  • ORACLE supports more than 50 zones (was only seeing the first 50) (#3179) (@fabienmazieres)
  • ORACLE now properly handles the API's inconsistent handling of "trailing dot" on NS records (#3170) (@fabienmazieres)
  • M365_BUILDER no longer fails on second level domains (#3165) (@CJFelto)
  • Security fix: github.com/go-acme/lego to v4 to resolve security issue (#3169) (@jauderho)
  • Integration test TestDualProviders cleans up after itself better (#3171) (@fabienmazieres)

Thanks to everyone for their contributions! This is a community-driven project and we couldn't do it without all your PRs, reviews, and other support!

Here's the details:

Changelog

Provider-specific changes:

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.

Contributors

jauderho, xddxdd, and 5 other contributors
Assets 14
Loading

v4.14.0

16 Oct 18:39
@github-actions github-actions
v4.14.0
2bb0d87
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.14.0

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.

Contributors

systemcrash, chicks-net, and 9 other contributors
Assets 14
Loading

v4.13.0

03 Sep 22:12
@github-actions github-actions
v4.13.0
74826d3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.13.0

Hello DNS fans!

This release introduces one new provider and many small fixes and improvements.

  • NEW PROVIDER: Sakura Cloud (SAKURACLOUD) (thanks to @ttkzw!)
  • NEW FEATURE: The HASH() function can generate hash strings. (thanks to @fuero!)
  • Improvements to providers: AUTODNS now supports PTR records, GANDI_V5 supports their new authentication system, HUAWEICLOUD has better DNSSEC support, NS1 documents that NS1_URLFWD is going away, ORACLE now abides by rate- limits automatically, PORKBUN now supports URL forwarding, and POWERDNS has added some reliability improvements.

Some big changes are coming:

  • #3108 the "change count" is moving out of the individual provider code, into the main code. This will make the "# corrections" count more accurate.
  • #3082 investigates making it easier to add new DNS types (A, MX, etc).

Learning Go? Interested in a starter project? Please email tlimoncelli at stackoverflow dot com.

  • 23 providers still use diff.NewCompat() instead of the new diff2.By* functions. There's nothing wrong with that, but upgrade will make the code cleaner, more simple, and might make the "preview" output cleaner.
  • I have a few other refactoring ideas that will clean up the code. Interested? Let me know!

Thanks to everyone for their contributions! This is a community effort and it wouldn't be a success without all your help!

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.

Contributors

fuero, llange, and 10 other contributors
Assets 14
Loading

v4.12.5

18 Jul 19:13
@github-actions github-actions
v4.12.5
0869052
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.12.5

Hello DNSControl fans!

This is another bugfix release. Only CLOUDFLAREAPI is affected, and only the CF_REDIRECT/CF_TEMP_REDIRECT/CF_SINGLE_REDIRECT commands are affected.

Some non-functional improvements are included in this release too. @cafferata contributed code that automatically generates the OWNERS file, @nikolamilekic and @svenluijten fixed documentation bugs.

Cloudflare-related improvements:

  • Bug fixed: CF_SINGLE_REDIRECT rule name was not propagating to Cloudflare correctly. #3049
  • Bug fixed: CF_REDIRECT/CF_TEMP_REDIRECT rule name generated in conversion mode was long and ugly; now they are short and easier to identify. They are in the (1,302,when,then) format seen in preview output.
  • New feature: Log the CF_SINGLE_REDIRECT statements generated when CF_REDIRECT/CF_TEMP_REDIRECT is in conversion mode.

Explanation of the new feature:

Suppose dnsconfig.js includes a statement like:

D("example.com", ...
    CF_TEMP_REDIR("https://example.com/*", "https://replacement.example.com/$1),

In the old days, CF_TEMP_REDIR would generate a Cloudflare "page rule". However page rules are going away. Therefore, these will now be silently translated into CF_SINGLE_REDIRECT statements when the manage_single_redirects meta feature is set to true. A log of these translations can be generated by setting the transcode_log variable:

var DSP_CLOUDFLARE = NewDnsProvider("cloudflare", {
    "manage_single_redirects": true,
    "transcode_log": "transcode.log",
});

Once set, any such translations will be appended to the filename transcode.log.

In this example, the log will look like this:

D("example.com", ...
    CF_SINGLE_REDIRECT("1,302,https://example.com/*,https://replacement.example.com/$1",
                       302,
                       'http.host eq "example.com"',
                       'concat("https://replacement.example.com", http.request.uri.path)'
    ),

Replacing the old CF_TEMP_REDIR statement with the above CF_SINGLE_REDIRECT statement requires manual cutting and pasting.

While the CF_REDIRECT/CF_TEMP_REDIRECT statements are not going away, it is recommended that you convert to CF_SINGLE_REDIRECT since they are more flexible and officially supported by Cloudflare.

This feature is documented in https://docs.dnscontrol.org/provider/cloudflareapi#old-style-vs-new-style-redirects

Changelog

Provider-specific changes:

Documentation:

CI/CD:

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.

Contributors

cafferata, nikolamilekic, and 2 other contributors
Assets 14
Loading

v4.12.4

09 Jul 19:47
@github-actions github-actions
v4.12.4
0ed31ef
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.12.4

Hello DNSControl fans!

This is another bugfix release. More fixes for the CF_SINGLE_REDIRECT() feature (now it actually works!), plus removed an debug statement that should have been removed before release, and some docs and dependency upgrades.

"This time for sure!" --Bullwinkle

Changelog

Provider-specific changes:

Documentation:

CI/CD:

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.

Contributors

cafferata, tlimoncelli, and dependabot
Assets 14
Loading