Home
last modified time | relevance | path

Searched refs:NXDOMAIN (Results 1 – 9 of 9) sorted by relevance

/external/dnsmasq/src/
Dnameser.h131 #define NXDOMAIN 3 /* non existent domain */ macro
Dforward.c357 if (header->opcode != QUERY || (header->rcode != NOERROR && header->rcode != NXDOMAIN)) in process_reply()
368 if (daemon->bogus_addr && header->rcode != NXDOMAIN && in process_reply()
371 header->rcode = NXDOMAIN; in process_reply()
374 if (header->rcode == NXDOMAIN && extract_request(header, n, daemon->namebuff, NULL) && in process_reply()
Drfc1035.c540 int flags = header->rcode == NXDOMAIN ? F_NXDOMAIN : 0; in extract_addresses()
748 header->rcode = NXDOMAIN; in setup_reply()
1354 header->rcode = NXDOMAIN; in answer_request()
/external/tcpdump/
Dnameser.h115 #define NXDOMAIN 3 /* non existent domain */ macro
/external/rust/crates/grpcio-sys/grpc/third_party/cares/cares/
Dnameser.h146 #define NXDOMAIN ns_r_nxdomain macro
Dares_query.c173 case NXDOMAIN: in qcallback()
/external/mdnsresponder/
DPrivateDNS.txt18 when necessary. After receiving an NXDOMAIN error, mDNSResponder checks
26 key, the call fails as it initially did, with an NXDOMAIN error.
139 queries that initially result in an NXDOMAIN error. This behavior might
/external/dnsmasq/
DCHANGELOG.archive369 Cache and return the NXDOMAIN status of failed queries:
574 forwarded because -D is in effect, return NXDOMAIN not
1088 Change behaviour of "bogus-priv" option to return NXDOMAIN
1195 Fixed NXDOMAIN/NODATA confusion for locally known
1200 is still tried upstream, but a NXDOMAIN reply gets
2362 Fix a bug where NXDOMAIN could be returned for a query
2366 An IPv6 query for name.domain would return NXDOMAIN, and
Ddnsmasq.conf.example451 # have dnsmasq instead return the correct NXDOMAIN response, uncomment