This very small change sets a zone's default TTL to None for all new and updated zones, as well as for all existing zones via a data migration.
As a result, NS records will still follow the zone's default TTL if the zone data are created with a $TTL tag or similar mechanism in place (which is recommended anyway to avoid falling back to the SOA MINIMUM_TTL setting for successful queries).
@hatsat32: This PR can't be merged together with #240 as both have migrations. That needs to be fixed when the merge conflict pops up.
fixes #242
This very small change sets a zone's default TTL to None for all new and updated zones, as well as for all existing zones via a data migration.
As a result, NS records will still follow the zone's default TTL if the zone data are created with a
$TTL
tag or similar mechanism in place (which is recommended anyway to avoid falling back to the SOAMINIMUM_TTL
setting for successful queries).@hatsat32: This PR can't be merged together with #240 as both have migrations. That needs to be fixed when the merge conflict pops up.