diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-01-18 22:33:23 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-01-18 23:31:16 +0100 |
| commit | 542e0c84d1518a1515e03194dd25299b2652778c (patch) | |
| tree | 0c862d869f25f16a2239cbc612165409abc47a3d /src/resolve/resolved-dns-question.h | |
| parent | 59a899908f9f1ead3cdb8b87ff98225054b5dab0 (diff) | |
resolved: never consider following a CNAME/DNAME chain for a CNAME/DNAME lookup
Let's avoid thinking that a CNAME/DNAME chain traversal could be a good idea if QTYPE is already CNAME/DNAME.
(Also, let's bail out early when trying to see if some RR is a suitable CNAME/DNAME for some other RR).
Diffstat (limited to 'src/resolve/resolved-dns-question.h')
| -rw-r--r-- | src/resolve/resolved-dns-question.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/resolve/resolved-dns-question.h b/src/resolve/resolved-dns-question.h index 7ca9224e6f..98e1f0e366 100644 --- a/src/resolve/resolved-dns-question.h +++ b/src/resolve/resolved-dns-question.h @@ -45,7 +45,7 @@ int dns_question_new_service(DnsQuestion **ret, const char *service, const char int dns_question_add(DnsQuestion *q, DnsResourceKey *key); int dns_question_matches_rr(DnsQuestion *q, DnsResourceRecord *rr, const char *search_domain); -int dns_question_matches_cname(DnsQuestion *q, DnsResourceRecord *rr, const char* search_domain); +int dns_question_matches_cname_or_dname(DnsQuestion *q, DnsResourceRecord *rr, const char* search_domain); int dns_question_is_valid_for_query(DnsQuestion *q); int dns_question_contains(DnsQuestion *a, const DnsResourceKey *k); int dns_question_is_equal(DnsQuestion *a, DnsQuestion *b); |