Description
Currently we are solving potential splitbrain situation of zone delegation configuration by putting timestamp as TXT to heartbeat dns record in edgeDNS zone. Implementation details are in #44
During e2e tests we realized that TTL for this TXT record is implicitly inherited by dns zone configuration of Infoblox.
When TTL is longer then we have an obvious problem with liveness check incorrectness.
We need to find a reliable way to control TTL of edgeDNS splitbrain TXT records.
Current hypo is to use special API call of TTL update
It will also require another upstream modification of https://github.com/infobloxopen/infoblox-go-client as it does not support TTL handling.
Issue is still workaroundable by setting low TTL in edgeDNSzone configuration in Infoblox
Activity