Changeset 995 for branches/cname-collision/dnsdb.conf

Timestamp:

01/22/26 18:11:32 (2 weeks ago)

Author:

Kris Deugau

Message:

/branches/cname-collision

Add a configuration option to set how to handle several cases of overlapping
timestamp expiry/valid-after cases checking for CNAME collisions
See #72

File:

• branches/cname-collision/dnsdb.conf (modified) (1 diff)

branches/cname-collision/dnsdb.conf

@@ -60 +60 @@
 #lowercase = 0
 
+# Variously coerce timestamp and valid-after/expiry flags onto a new/updated record if the
+# record as requested would cause a CNAME to overlap with another record.
+# adjust:  Adjust the timestamp where an expiry+valid-after would overlap
+#   - existing record expires, new record has valid-after before expiry => adjust timestamp to match existing record
+#   - existing record is valid-after, new record has expiry after valid-after => adjust timestamp to match existing record
+# none: (default) Do not make changes to timestamps to avoid overlap
+#coerce_cname_timestamp = none
+
 # Show formal .arpa zone name instead of the natural IP or CIDR for reverse zone names and records?
 # Valid values are none, zone, record, or all