Custom Query (2195 matches)

Currently if the replace UDP socket fail, the transport will be restarted when receiving data or write event triggered.

This ticket will restart the UDP transport when the sending fail.

The ​standard stated:

DNS resolvers and recursive servers MUST support UDP, and
SHOULD support TCP, for sending (non-zone-transfer) queries.
Specifically, a DNS resolver or server that is sending a
non-zone-transfer query MUST send a UDP query first.  If the
Answer section of the response is truncated and if the
requester supports TCP, it SHOULD try the query again using
TCP.

.........
         
Truncated responses MUST NOT be saved (cached) and later
used in such a way that the fact that they are truncated is
lost.

Instead of following up with a TCP query which is unsupported, currently the library will follow up with DNS A query. Based on the recommendation above, it's better to discard the response and raise error.

Thanks to Daniel Schopf for the report.

Assertion occurs in pj_dns_resolver_start_query() as it tries to resolve A/AAAA record of an empty target.

Thanks Andrey Kovalenko for the report.