This one time, at band camp, Edward Buck said: > In this case, the algorithm does not match the specification. > Therefore, it's a bug. > > Quoting the man page: > > "Resolver queries having fewer than ndots dots (default is 1) in them > will be attempted using each component of the search path in turn until > a match is found." > > IPv6 queries are not excluded from this description. The fact is that > with this bug, resolver queries with MORE than ndots are ALWAYS > attempted using each component of the search path. Yes, the queries are > IPv6 but that does not matter. > > If you read further down the man page: > > "ndots:n sets a threshold for the number of dots which must appear in a > name given to res_query() (see resolver(3)) before an initial absolute > query will be made." > > There's no ambiguity in the term 'absolute query'. A lookup for the > IPv6 address example.com.domain.in.search.path is NOT an initial > absolute query no matter how you look at it. Unless of course you missed the part of the report where the query under discussion has greater than ndots in it. The original query under discussion was mx1.hotmail.com, and ndots was unset, so defaulted to 1. There are 2 dots in mx1.hotmail.com, so the search order was correctly used. That it defaulted to ipv6 first is the only thing really left for discussion, it seems to me. -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : sgran@debian.org | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
Attachment:
signature.asc
Description: Digital signature