RFC 2181 section 5.2 says that differing TTLs in RRSet with the same label/class/type should be deprecated with the behavior that an authoritative server should reply with all the TTLs set to the lowest TTL in the RRSet:
"Should an authoritative source send such a malformed RRSet, the client should treat the RRs for all purposes as if all TTLs in the RRSet had been set to the value of the lowest TTL in the RRSet." I noticed that BIND 9.8.2 is choosing the HIGHEST TTL, not the lowest. Is this a bug, or was there a newer RFC that changed the required behavior? _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
