On 8/10/17 4:07 PM, Viktor Dukhovni wrote:
> Under that condition, there's no need to wait to remove the TXT
> record, removal of the record (being a change in the record) will
> in this variant of the design trigger a refresh, and the sending
> MTA will see a "none" policy and proceed to promptly flush it.
That's the part I didn't get: that an NXDOMAIN or NODATA response was
also considered to be a record change that triggers a refresh. Thanks.
That isn't immediately obvious because the lack of a TXT record when you
don't already have a policy cached inhibits fetch of the policy.
Uta mailing list