Re: Leopard Name Resolution Issues

--On 27 November 2007 22:50:17 -0800 John Musbach <johnmusbach@...>
wrote:

> One thing to try is set your dns servers to the following opendns servers:
>
> 208.67.222.222 and 208.67.220.220...
>
> ping the hostname, then set the dns server back to the address of your
> airport wireless device and try pinging again

Believe it or not, I already tried that. It gave me the following truly
bizarre result:

dmz@whitestar ~/courses/current =( ping babylon4.tffenterprises.com
PING babylon4.tffenterprises.com.insttech.washington.edu (208.67.219.137):
56 data bytes
(successful pings)

As it happens, my DNS search path includes the following:

local
tffenterprises.com
insttech.washington.edu
washington.edu

So what seems to have happened with the ping is that the local resolver
couldn't find the host at the name I actually typed... so it decided to
tack insttech.washington.edu on the end, creating a nonexistent hostname
that OpenDNS's apparently-fundamentally-misconfigured DNS servers resolved
to their catchall address of 208.67.219.137 (going to
http://babylon4.tffenterprises.com.insttech.washington.edu/ to satisfy my
curiosity gave me a page that helpfully asked me if I was looking for the
University of Washington website - yay!).

So... same problem, it seems, regardless of the DNS server I'm using.
Definitely not a server-side issue.

Anybody have any ideas on client-side issues with Leopard's resolver that
might cause this sort of problem?

-Dan

------------------------------------------------------------------
Daniel M. Zimmerman                                TFF Enterprises
1900 Commerce St. Box 358426   http://www.tffenterprises.com/~dmz/
Tacoma, WA  98402  USA                      dmz@...
_______________________________________________
MacOSX-admin mailing list
MacOSX-admin@...
http://www.omnigroup.com/mailman/listinfo/macosx-admin