Aquesta és una versió anterior. La versió actual és la 5.7.1. DNSControl 5.7.1 · Data de publicació:
Fitxers d’instal·lació 4.28.2
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| ARM64 | ZIP → Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
Greetings DNS fans!
This is a bugfix release. BIND users discovered that "push" was regenerating zonefiles even when there was no change. The reason was that the %D verb was always "" (null string). Shout out to @ondohotola for quickly reporting this bug and confirming the workaround. A full fix is included in v4.28.2.
This release also includes some documentation and tool improvements.
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 3rd Monday 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
Documentation:
- 986bc4c5f4b67edac46c197abfcecb080b7a6f0e: DOCS: replace all NewRegistrar('ThirdParty') (#3889) (@SukkaW)
Dependencies:
- 08a6fa6ec4d78bf31e66ec5914215873b00ff1f7: CHORE: Update deps, regenerate docs (#3902) (@tlimoncelli)
Other changes and improvements:
- 0ae4acc3e4f1c254226313a62a7017a97478d6ea: BUGFIX: BIND %D not working after v4.28.0 (#3900) (@tlimoncelli)
- 865dad5b786f92915bf0690f7f31ea32ca76a1c4: TOOLS: bin/generate-all.sh should skip .vscode (#3901) (@tlimoncelli)
- db27a1e557baacb644ff14692668f5367237343d: [docs] Refresh digital ocean provider docs (#3860) (@chicks-net)
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
- 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.https://github.com/StackExchange/dnscontrol/releases/tag/v4.28.2
