New release: dnscontrol v4.3.0
Tom Limoncelli
v4.3.0
This release introduces a new provider (Mythic Beasts), a new notification target (Telegram), and brings the most computer-science-y feature we've ever added: Ordered updates.
Order updates means that changes will be ordered with respect to dependencies. For example when creating an A record and a CNAME that points to that A record, DNSControl will always try to create the A record first, so that when the CNAME is created it is pointing to a target that already exists. When removing records, the targets must be removed before their dependents (dependenters?). Some DNS providers require this kind of ordering and the provider code had to carefully re-order updates. Now this is done for the provider.
Due to the complexity of DNS, when adding, removing, and modifying records this ordering process can be very difficult to get right!
Because this feature is new and might still have bugs, it can be disabled with the --disableordering flag. (dnscontrol --disableordering preview)
Thanks to @blackshadev for delivering this feature (and putting up with all my suggestions along the way!)
Changelog
Major features:
- e32bdc0: NEW FEATURE: Order changes based on the record dependencies (#2419) (@blackshadev)
- 5416793: NEW PROVIDER: Mythic Beasts DNS (#2528) (@tomfitzhenry)
- e26afaf: New feature: Telegram Notifier (#2503) (@chrisbrownie)
Provider-specific changes:
- 7e2e3bd: AUTODNS: Added CAA records (#2533) (@prey87)
- d8047eb: OVH: allow native OVH records for DKIM, etc. to be managed (#2535) (@masterzen)
Other changes and improvements:
- c2eb989: DOCS: Improved docker instructions (#2532) (@tlimoncelli)
- a7fe17a: Display changes, even if upstream has no records. (#2531) (@tomfitzhenry)
- c69bd43: Doc fixes noticed while writing a provider (#2530) (@tomfitzhenry)
- 8bf996b: Strip ANSI color codes from notifications (#2508) (@costasd)