Lines Matching refs:queries
32 BIND 8.4.7 and BIND 9.3.2. Differences in answers to captured queries from
50 Our method uses a set of queries captured from production name servers.
51 These queries are sent over UDP to a name server set up to serve a
78 and played the queries against the authoritative name servers.
104 \subsection{Comparison of responses to root queries}
145 \subsection{Comparison of responses to NL TLD queries}
184 NSD clears the DO bit in answers to queries with the DO bit. BIND copies the
199 NSD clears the CD bit in answers to queries with the CD bit. BIND copies the
206 by recursive servers. BIND copies the CD bit for some formerr queries.
233 Some update, ixfr request, notify, gss-tsig TKEY sequence queries could
242 \subsubsection{b-soattl - BIND sets SOA TTL in authority section to 0 for SOA queries}
316 A difference in behaviour for CLASS=ANY queries. For existing domains both
379 nxdomain queries.
383 some bad queries}
389 also NXDOMAIN to NOTIFY queries). All these queries are malformed in
393 is a query packet of 18 zero bytes. For some queries no answer
394 only happens when BIND is presented with a trace of queries, not for
400 some internal state of BIND is affected by earlier queries.
403 queries that are too short, or that have the QR bit set. NSD tries to be
419 BIND and NSD give different errors for notify queries. The servers are started
449 BIND does not implement queries for the MAILB type. NSD treats it as
454 \subsubsection{d-version - BIND returns servfail on version.server queries}
461 Both NSD and BIND return version.bind queries of the chaos class.
462 These queries differ in the version number they return, of course.
463 BIND does not return version.server queries. This is a design decision
464 on the part of NSD to return version.server queries with the same answer.
471 to queries from the root. These answers are 480+ bytes long.
512 To queries for IXFR BIND responds with a valid answer (the latest SOA)
524 the DNS header section. For some queries, NSD includes an EDNS record in
537 BIND includes the query section in reply to unparseable queries. NSD does not.
548 For queries with an unknown class in the query, BIND includes the query section
559 For queries that are bad packets, with malformed RRs, with an unknown opcode,
573 For queries to a domain that is not served, which can only have arrived at
584 \subsubsection{b-noglue-nsquery - BIND returns no glue for NS queries}
587 For queries for the NS records of the zone, BIND does not include glue
599 For queries without a question section the error code differs.
615 NSD does not give a formerr on these queries, it processes them.
666 To queries for version.bind and version.server the different implementations
682 Default config denies all notify queries for NSD 3. These answers are correct
708 with queries for the root zone are below.
738 with queries for the .nl zone are below.
761 For NXDOMAIN queries in root-servers.net BIND 8 uses the minimum TTL from
771 \subsection{b8-badquery-ignored - BIND 8 replies normally for some bad queries}
774 BIND8 manages to reply for malformed queries. NSD replies with FORMERR.
781 \subsection{b8-badedns0 - BIND 8 ignores bad EDNS0 queries}
784 BIND 8 ignores queries with bad EDNS0 section. It answers the query.
793 \subsection{b8-auth-any - BIND 8 includes an authority section on queries for ANY .}
796 BIND8 includes an authority section on queries for class ANY .
804 \subsection{b8-ignore-tc-query - BIND 8 ignores the TC bit in queries}
807 BIND responds to queries that have the TC bit set. NSD gives FORMERR.
813 NSD is less liberal in accepting queries, it returns form error on queries with