Changeset 1018 for branches/cname-collision/DNSDB.pm
- Timestamp:
- 02/05/26 12:24:47 (3 days ago)
- File:
-
- 1 edited
-
branches/cname-collision/DNSDB.pm (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
branches/cname-collision/DNSDB.pm
r1013 r1018 729 729 } else { 730 730 if ($self->{coerce_cname_timestamp} eq 'adjust') { 731 # coerce the valid-after timestamp 732 ${$args{stamp}} = strftime('%Y-%m-%d %H:%M:%S', localtime($t[0])); 733 return ('WARN', $typemap{${$args{rectype}}}." ".($args{update} ? 'updated' : 'added'). 731 if ($t[2] == 1) { 732 # found a valid-after, but it's in the past, so adding an expiring record to match doesn't make 733 # sense since it's effectively expired. 734 ##fixme: should probably remove this case once we get around to stripping valid-after timestamps once exported as active 735 return ('FAIL', "Cannot ".($args{update} ? 'update' : 'add')." ".$typemap{${$args{rectype}}}. 736 ", an existing valid-after record is already active for this name"); 737 } else { 738 # coerce the expiry timestamp 739 ${$args{stamp}} = strftime('%Y-%m-%d %H:%M:%S', localtime($t[0])); 740 return ('WARN', $typemap{${$args{rectype}}}." ".($args{update} ? 'updated' : 'added'). 734 741 " with modified valid-after time; conflicting expiring record found"); 742 } 735 743 } else { 736 744 # New valid-after overlaps existing expiry, and not configured to adjust it
Note:
See TracChangeset
for help on using the changeset viewer.
![[ DNS Administrator ]](/fx/dnsadmin-logo.png)