mDNS: the host does not support NSEC record. (IDFGH-9699) #258
Assignees
Comments
github-actions
bot
changed the title
david-cermak
added a commit
to david-cermak/esp-protocols
that referenced
this issue
Mar 30, 2023
MAJOR CHANGE: According to RFC6762-6.1, mdns must provide NSEC record in the addtional fields, if the host exclusively owns the queried name, but has no answer for the queried type. Closes espressif#258
david-cermak
added a commit
to david-cermak/esp-protocols
that referenced
this issue
Apr 14, 2023
MAJOR CHANGE: According to RFC6762-6.1, mdns must provide NSEC record in the addtional fields, if the host exclusively owns the queried name, but has no answer for the queried type. Closes espressif#258
espressif-bot
added
Status: In Progress
and removed
Status: Selected for Development
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
The host with no associated IPv6 addresses receives a AAAA record question query, the mDNS responds nothing. Accord to the RFC6762 6.1 section, the NSEC record is required to add the addtional response.
Describe the solution you'd like.
I hope the mDNS's responder can repond the DNS NSEC record to the question querier, when the question's resource record does not exist.
Describe alternatives you've considered.
No response
Additional context.
The feature is preferable to the querier having to retransmit its query multiple times, and eventually give up with a timeout.
The text was updated successfully, but these errors were encountered: