Corrupt cache

[Barry Margolin]

In article <9s9s0n$sue at pub3.rc.vix.com>,
Kevin Darcy  <kcd at daimlerchrysler.com> wrote:
>A better question is: why were you querying names like www.bingo-lan.org.com in
>the first place? Do you have some screwy resolver configuration somewhere on your
>network?

Before the "search" directive was added to resolv.conf, the BIND resolver
had an implicit search list based on the "domain" directive.  If you had:

domain a.b.c

it was implemented like:

search a.b.c b.c c

So with such a resolver, if your default domain were something.com, and you
tried to look up www.bingo-lan.org, it would try
www.bingo-lan.org.something.com, www.bingo-lan.org.com, then
www.bingo-lan.org (this early resolver also appended the default domains
even if the name was already qualified -- only a trailing "." prevented it).

See RFC 1535 for a full description of this problem.  The organizations who
registered domains of the form <gtld>.<gtld> have put in these wildcard
records specifically to catch people with these archaic resolvers.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.