Ignore:
Timestamp:
01/22/26 18:11:32 (10 days 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:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/cname-collision/DNSDB.pm

    r990 r995  
    284284    warn "Bad showrev_arpa setting $self->{showrev_arpa}, using default\n";
    285285    $self->{showrev_arpa} = 'none';
     286  }
     287  if (!grep /$self->{coerce_cname_timestamp}/, ('none','adjust','full')) {
     288    warn "Bad coerce_cname_timestamp setting $self->{coerce_cname_timestamp}, using default\n";
     289    $self->{coerce_cname_timestamp} = 'none';
    286290  }
    287291
     
    23272331      $cfg->{lowercase}         = $1 if /^lowercase\s*=\s*([a-z01]+)/i;
    23282332      $cfg->{showrev_arpa}      = $1 if /^showrev_arpa\s*=\s*([a-z]+)/i;
     2333      $cfg->{coerce_cname_timestamp}    = $1 if /^coerce_cname_timestamp\s*=\s*([a-z]+)/i;
    23292334      $cfg->{template_skip_0}   = $1 if /^template_skip_0\s*=\s*([a-z01]+)/i;
    23302335      $cfg->{template_skip_255} = $1 if /^template_skip_255\s*=\s*([a-z01]+)/i;
Note: See TracChangeset for help on using the changeset viewer.