Skip to content

v0.2.3: Bugfix for duplicate name / rename issue
Compare
Choose a tag to compare
@erikh erikh released this 28 Jul 05:07
· 239 commits to main since this release
v0.2.3
34dc09a

#94 exposed a serious bug where when renaming nodes, the record set would be appended to, not replaced. This resulted in a number of issues with A and AAAA records showing two independent IPs for the named record, one for each point-in-time ip assignment.

Summarily:

bob -> 1.2.3.4
alice -> 1.2.3.5

then rename alice to bob, and bob to snuffy

snuffy -> 1.2.3.4
bob -> 1.2.3.4, 1.2.3.5 // wrong!!!

Previously to this patch a restart of the service will resolve things, as zeronsd is stateless and cannot be corrupted persistently.

Builds are available for the usual platforms, including docker and homebrew via our homebrew-tap.

Assets 5
Loading