X-Git-Url: http://gitweb.michael.orlitzky.com/?a=blobdiff_plain;f=doc%2Fman1%2Fhaeredes.1;h=ea09e2d1898af49656b48045faa6668758c6bf79;hb=689bda2499ec821772b456cb7982527d6740649f;hp=900b4c64e195bc044fc68c149b6b178dc3afb778;hpb=f9610a6d357f2ed79f2f18baa477244970f8b40f;p=haeredes.git diff --git a/doc/man1/haeredes.1 b/doc/man1/haeredes.1 index 900b4c6..ea09e2d 100644 --- a/doc/man1/haeredes.1 +++ b/doc/man1/haeredes.1 @@ -91,6 +91,28 @@ example, to use 10 threads, .nf $ haeredes [OPTIONS] [DELEGATES] \fI+RTS -N10\fR .fi +.SH DNS ERRORS +.P +There are three types of DNS errors that can occur: +.nr step 1 1 +.IP \n[step] 2 +Timeouts. If the query times out, we don't get an answer back. The +timeout can be adjusted with the \fB\-\-timeout\fR flag. +.IP \n+[step] +Sequence number mismatches. Every DNS query is sent with a sequence +number; if the response has a different sequence number than the one +we sent, something is wrong (foul play, or a bug somewhere in the +stack). +.IP \n+[step] +Unexpected RDATA. If we ask for an \fIA\fR record, we expect to get a +response for an \fIA\fR record. If we get something else -- well, +something went wrong. +.P +Haeredes is designed to ignore these errors. A timeout or bad response +to a query is not an indication that something is wrong with the DNS +for the supplied domains. There might be something else wrong with +your (caching/recursive) DNS infrastructure, but it isn't one of the +problems that Haeredes is designed to detect. .SH OPTIONS .IP \fB\-\-no\-append\-root\fR,\ \fB-n\fR @@ -148,6 +170,15 @@ know .invalid will not be delegated): .I $ haeredes <<< \(dqexample.invalid\(dq Domain \(dqexample.invalid.\(dq not delegated. .fi +.IP \[bu] +Set the timeout to one second, and query a nonexistent +nameserver. This should result in a timeout, which will be ignored per +the discussion in \fBDNS ERRORS\fR: + +.nf +.I $ haeredes --timeout=1 --server 10.1.46.12 ns1.example.com \\\\ +.I " <<< \(dqexample.com\(dq" +.fi .SH BUGS .P Send bugs to michael@orlitzky.com.