[GH-ISSUE #395] mDNS needs an active DNS listener #475

New issue

Open

opened 2026-03-15 22:43:38 +03:00 by kerem · 1 comment

kerem commented

2026-03-15 22:43:38 +03:00

Owner

Originally created by @bluejekyll on GitHub (Apr 11, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/395

I just noticed a bug rereading the RFC: https://tools.ietf.org/html/rfc6762#section-19

* ignores the Query ID field (except for generating legacy responses), I definitely look for the query_id on all responses still.

Originally created by @bluejekyll on GitHub (Apr 11, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/395 I just noticed a bug rereading the RFC: https://tools.ietf.org/html/rfc6762#section-19 `* ignores the Query ID field (except for generating legacy responses)`, I definitely look for the query_id on all responses still.

kerem added the

crate:proto

crate:resolver

feature:mdns

labels

2026-03-15 22:43:38 +03:00

kerem commented

2026-03-15 22:43:49 +03:00

Author

Owner

@bluejekyll commented on GitHub (Apr 24, 2018):

This will require more significant changes, such as an active mDNS listener updating cache. The cache will then need some way to notify a query listener of the updates received in the listener.

For now, we'll use the fallback query mechanism in mDNS to respond as a class UDP request.

@bluejekyll commented on GitHub (Apr 24, 2018): This will require more significant changes, such as an active mDNS listener updating cache. The cache will then need some way to notify a query listener of the updates received in the listener. For now, we'll use the fallback query mechanism in mDNS to respond as a class UDP request.

kerem referenced this issue

2026-03-16 02:07:50 +03:00

[PR #475] [MERGED] Update version in docs #1462