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-query.c | |
| 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-query.c')
| -rw-r--r-- | src/resolve/resolved-dns-query.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/resolve/resolved-dns-query.c b/src/resolve/resolved-dns-query.c index 2938238f27..1b7083d7dc 100644 --- a/src/resolve/resolved-dns-query.c +++ b/src/resolve/resolved-dns-query.c @@ -1268,7 +1268,7 @@ int dns_query_process_cname(DnsQuery *q) { if (r > 0) return DNS_QUERY_MATCH; /* The answer matches directly, no need to follow cnames */ - r = dns_question_matches_cname(question, rr, DNS_SEARCH_DOMAIN_NAME(q->answer_search_domain)); + r = dns_question_matches_cname_or_dname(question, rr, DNS_SEARCH_DOMAIN_NAME(q->answer_search_domain)); if (r < 0) return r; if (r > 0 && !cname) |