Baixar DNSControl 5.4.0 per a Windows

Greetings DNS fans!
New provider!
DNSControl now supports CloudPress DNS! Thanks to @arnoschoon for submitting this!
Experimental: Try the new D() syntax!
We're experimenting with a new registrar/dns provider syntax. Try out this newer, more concise format:
D("example.com",
REGISTRAR("gandi_main"),
SERVICE("gandi_main"),
A("@", "192.0.2.1")
);
No REG_* or DSP_* variables. No muss, no fuss.
- More examples here.
- Please test it and share feedback!
- The old NewRegistrar()/NewDnsProvider()/DnsProvider() syntax still works, of course. We'll support those forever.
Like it? Hate it? Join the discussion here: https://github.com/orgs/DNSControl/discussions/4949
Unless someone finds a major problem, this will probably become the default in all documentation in a coming release. Until then, the format might change slightly.
Thanks!
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.
Changelog
Provider-specific changes:
- 89188fe393868680b99a5873404ca4eb5228ee7b: feat(p/BUNNYDNS): make the provider safe to run concurrently (#4980) (@jfexyz)
- 2b9883e2e4db3050ab33f90ebc87c241a1abdcdd: feat(p/DNSOVERHTTPS): mark the provider as verified for concurrency (#4981) (@jfexyz)
New features:
- 7e201d7b67a7455558e71a1714a1cefb2af87b23: feat(cloudpress): add CloudPress DNS provider (#4390) (@arnoschoon)
- c16964fbf2ae8f632dc5d51ba8a9622caa9b26d9: feat: Stage 5: Add SupportedTypes and exhaustive provider validation (#4967) (@TomOnTime)
- 1a6b48a0c0b7835519802fed8dd9b56674b0a86c: feat: Stage 6a: support domain-specific DNS provider metadata (#4975) (@TomOnTime)
- b45d6ddd85ccbffa6827a2d5aadbf054c5a49a9a: feat: Suppress "Serially checking"/"Serially Gathering " messages unless --full flag used (#4978) (@jfexyz)
- 0136f8c94c777befdf142e8f57c09ee7a241ec31: feat: add SKIP_AUDIT modifier (#4971) (@GZTimeWalker)
- c9bf25dcee574cb65dadf0224064adcdffe245b4: feat: reduce messages if all providers are concurrent (--full overrides) (#4979) (@TomOnTime)
- 8d96a606fcc65c21d4eccc7579692cb512f29e21: feat: stage 6b: add direct REGISTRAR/SERVICE syntax (#4976) (@TomOnTime)
Refactoring:
- d2f5fb9733e120718087f72fcae7b944194f2d3c: refactor: Stage 2: Adopt new way for providers to register, test with 4 providers (#4956) (@TomOnTime)
- 93b3df78ba383f746a76a59576e72c564541da7f: refactor: Stage 3: Migrate remaining providers to providers.Register (#4965) (@TomOnTime)
- 76ddb69a03fc5b6a0ef3deec356b7c897912d300: refactor: Stage 4: Remove legacy provider registrations, accessors, etc (#4966) (@TomOnTime)
- ed4a220f7ba5c638cefb779d0aada0f69c553ec4: refactor: Stage 6: Adopt SupportedTypes across providers (#4968) (@TomOnTime)
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.