This is unnecessary. All the rule does is limit the process to class IN zones.
UPDATE, IXFR and AXFR are class agnostic.
1. TIMEOUT resource records are only defined for CLASS IN.
This seems overly restrictive. I would allow TIMEOUT records that
match added records to be accepted.
5. TIMEOUT resource records cannot be directly added, modified, or
deleted through DNS Update.
Secondary servers that are TIMEOUT aware should ignore TIMEOUT records
beyond storing them in case the server get promoted to being the master.
Is the secondary going to be able regenerate the RRset as the records are
removed as well as generate and sign NSEC and NSEC3 records?
Sources of TIMEOUT Expiry Time
Add matching TIMEOUT records added via UPDATE.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
