diff options
author | Tom Gundersen <teg@jklm.no> | 2015-09-04 01:58:20 +0200 |
---|---|---|
committer | Tom Gundersen <teg@jklm.no> | 2015-09-16 17:03:18 +0200 |
commit | 5eefe544efbfbbd0d0026ca28913a9e82fec187c (patch) | |
tree | 99ef11732f301e00ac213d58a91690dd4f9b66f8 /src/resolve/resolved-dns-rr.c | |
parent | 5643c00afe29eae4b2e3575277038e60e6967d09 (diff) |
resolved: cache - cache what we can of negative redirect chains
When a NXDATA or a NODATA response is received for an alias it may
include CNAME records from the redirect chain. We should cache the
response for each of these names to avoid needless roundtrips in
the future.
It is not sufficient to do the negative caching only for the
canonical name, as the included redirection chain is not guaranteed
to be complete. In fact, only the final CNAME record from the chain
is guaranteed to be included.
We take care not to cache entries that redirects outside the current
zone, as the SOA will then not be valid.
Diffstat (limited to 'src/resolve/resolved-dns-rr.c')
0 files changed, 0 insertions, 0 deletions