Home
last modified time | relevance | path

Searched refs:answers (Results 1 – 8 of 8) sorted by relevance

/Zephyr-latest/doc/connectivity/networking/api/
Ddns_resolve.rst15 Supported DNS answers are IPv4/IPv6 addresses and CNAME.
/Zephyr-latest/subsys/net/lib/dns/
Dllmnr_responder.c167 static void setup_dns_hdr(uint8_t *buf, uint16_t answers, uint16_t dns_id) in setup_dns_hdr() argument
185 UNALIGNED_PUT(htons(answers), (uint16_t *)(buf + offset)); in setup_dns_hdr()
DKconfig182 DNS answers will use the TTL (in seconds).
252 DNS answers will use the TTL (in seconds). A default value is 30
Dmdns_responder.c174 static void setup_dns_hdr(uint8_t *buf, uint16_t answers) in setup_dns_hdr() argument
193 UNALIGNED_PUT(htons(answers), (uint16_t *)(buf + offset)); in setup_dns_hdr()
/Zephyr-latest/samples/subsys/ipc/openamp_rsc_table/
DREADME.rst103 On the Linux console, send a message to Zephyr which answers with the :samp:`TTY {<addr>}:` prefix.
/Zephyr-latest/
DCODE_OF_CONDUCT.md131 For answers to common questions about this code of conduct, see the FAQ at
/Zephyr-latest/doc/releases/
Drelease-notes-2.0.rst390 * DNS fixes for non-compressed answers.
999 * :github:`16594` - net: dns: Zephyr is unable to unpack mDNS answers produced by another Zephyr no…
Drelease-notes-1.14.rst341 * :github:`16594` - net: dns: Zephyr is unable to unpack mDNS answers produced by another Zephyr no…