[GH-ISSUE #2905] Failing test: `name_server::rfc5155::wildcard_no_data_response` #1084

New issue

Open

opened 2026-03-16 01:34:24 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 01:34:24 +03:00

Owner

Originally created by @divergentdave on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2905

This test is currently failing. A request is made for an MX record at a subdomain, and the zone only contains an A record with a wildcard owner name. Thus, the name server should send a no data response, but it instead sends an NXDOMAIN response. build_authoritative_response() expects to receive errors of different types in order to produce both no data responses and NXDOMAIN responses. There's only one point in <InMemoryAuthority as Authority>::lookup() that produces LookupError::NameExists, and it does not currently check for wildcard records. All the wildcard traversal currently happens in InnerInMemory::inner_lookup() and InnerInMemory::inner_lookup_wildcard().

See draft PR #2457 regarding this test. This is also somewhat related to #2882, regarding validation of responses with wildcard expansion.

Originally created by @divergentdave on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2905 This test is currently failing. A request is made for an MX record at a subdomain, and the zone only contains an A record with a wildcard owner name. Thus, the name server should send a no data response, but it instead sends an NXDOMAIN response. `build_authoritative_response()` expects to receive errors of different types in order to produce both no data responses and NXDOMAIN responses. There's only one point in `<InMemoryAuthority as Authority>::lookup()` that produces `LookupError::NameExists`, and it does not currently check for wildcard records. All the wildcard traversal currently happens in `InnerInMemory::inner_lookup()` and `InnerInMemory::inner_lookup_wildcard()`. See draft PR #2457 regarding this test. This is also somewhat related to #2882, regarding validation of responses with wildcard expansion.