RRSET_TTL_MISMATCH

warning

Records that belong together carry different lifetimes, so some will disappear from resolvers before the others.

Working today, and one change away from not working.

How we know

No fixture produces this locally.

A zone file cannot express it. Measured: named-checkzone silently rewrites a mismatched TTL to the first one it saw, and nsd-checkzone warns — so a fixture would be normalised before it was served and the test would assert nothing. In the wild it comes from a server assembling an answer from several sources, or a resolver merging cached records. The comparison itself is pure and unit-tested.