diff options
author | Lennart Poettering <lennart@poettering.net> | 2017-02-13 20:34:39 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2017-02-13 20:34:39 +0100 |
commit | 4a46ed1bc69487a0f78ee35e32185ba146279312 (patch) | |
tree | b38c993f5059232eb02725b67b9aa329ba738c3d /src/resolve/resolved-dns-cache.c | |
parent | 53f7443a4302ca7950777f6140d7d87052a202d9 (diff) |
resolved: don't return ANY transactions when looking for transactions
This reverts a part of 53fda2bb933694c9bdb1bbf1f5583e39673b74b2:
On classic DNS and LLMNR ANY requests may be replied to with any kind of
RR, and the reply does not have to be comprehensive: these protocols
simply define that if there's an RRset that can answer the question,
then at least one should be sent as reply, but not necessarily all. This
means it's not safe to "merge" transactions for arbitrary RR types into
ANY requests, as the reply might not answer the specific question.
As the merging is primarily an optimization, let's undo this for now.
This logic may be readded later, in a way that only applies to mDNS.
Also, there's an OOM problem with this chunk: dns_resource_key_new()
might fail due to OOM and this is not handled. (This is easily removed
though, by using DNS_RESOURCE_KEY_CONST()).
Diffstat (limited to 'src/resolve/resolved-dns-cache.c')
0 files changed, 0 insertions, 0 deletions