diff options
| author | Lennart Poettering <lennart@poettering.net> | 2015-08-21 22:55:01 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2015-08-21 22:55:01 +0200 |
| commit | f52e61da047d7fc74e83f12dbbf87e0cbcc51c73 (patch) | |
| tree | 477d5ab7d178f3530699afc31b97a61b014d8e11 /src/resolve/resolved-dns-question.h | |
| parent | 9e08a6e0ce6ae37189666fd2517e643e971e45b1 (diff) | |
resolved: only maintain one question RR key per transaction
Let's simplify things and only maintain a single RR key per transaction
object, instead of a full DnsQuestion. Unicast DNS and LLMNR don't
support multiple questions per packet anway, and Multicast DNS suggests
coalescing questions beyond a single dns query, across the whole system.
Diffstat (limited to 'src/resolve/resolved-dns-question.h')
| -rw-r--r-- | src/resolve/resolved-dns-question.h | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/resolve/resolved-dns-question.h b/src/resolve/resolved-dns-question.h index fc98677798..77de0c7a2c 100644 --- a/src/resolve/resolved-dns-question.h +++ b/src/resolve/resolved-dns-question.h @@ -48,7 +48,4 @@ int dns_question_is_equal(DnsQuestion *a, DnsQuestion *b); int dns_question_cname_redirect(DnsQuestion *q, const char *name, DnsQuestion **ret); -int dns_question_endswith(DnsQuestion *q, const char *suffix); -int dns_question_extract_reverse_address(DnsQuestion *q, int *family, union in_addr_union *address); - DEFINE_TRIVIAL_CLEANUP_FUNC(DnsQuestion*, dns_question_unref); |