Is going to "http://somewhere.com." faster?

[Michael Voight]

Mark_Andrews at isc.org wrote:
> 
> > On Mon, 2 Aug 1999 Mark_Andrews at isc.org wrote:
> >
> > }
> > }     It is no longer "normal" behaviour and has not been for several
> > }     year.
> >
> > Please explain the conditions under which this is abnormal behaviour.
> >
> > }     If your resolver has this behaviour it contains a significant
> > }     security flaw.
> >
> > Again, please explain.  Only last week, I was looking into a resolution
> > problem under BIND 8.2.1.  With the trailing ".", dig would resolve the
> > name more quickly than without.
> 
>         Dig does *not* implement search list so it specifing a final dot
>         will have had *no* effect.  nslookup and the resolver implement
>         seach lists.  This is despite there being a seach arguement.
>

Not really, mileage may vary. nslookup and the resolver do NOT always
behave the same and do NOT always append the current domain name when
there is no trailing dot, as long as there is a dot...

Michael