On 11/01/2014 08:42, daniel.salzman(a)nic.cz wrote:
Hi Daniel,
Initially, we had just timestamps in zone dumps. I
prefer this, since
it makes smaller dumps and it is faster to process such records.
Afterwards,
we turned it off due to incompatibility with Bind. Because Bind is unable
to load these dumps if you need it.
I opened a bug report for BIND9, and Mark Andrews' response was that
unix timestamps should never have been allowed in the RFC, because it
breaks compatibility with older software. I disagree with him. BIND can
dump zones with human-readable timestamps if it wants to, but it should
*read* both formats, as should any software that claims to be RFC
4034-compliant.
Is there still anybody who requires human-readable
timestamps in zone
dumps from Knot?
If not, we probably disable this functionality.
You have my vote for disabling human-readable timestamps in zone dumps.
Regards,
Anand