Search Again:

Re: MacOS X Case-Sensitive DNS lookup bug

From: Aaron Lynch
Date: Thursday, May 24, 2001
Time: 2:17:24 am

On 5/24/01 1:44 AM, The Defendant "Men & Mice Support"
<cbuxton@menandmice.com> Confessed:

> lookupd is not just a DNS lookup tool. It's also the system's netinfo
> lookup daemon, as well as ldap and a few other things. Take a look at
> the techinfo page mentioned below and you'll see what I mean.
>
> I'm not all that familiar with the inner workings of Mac OS X, but it
> appears lookupd is the built-in resolver for all of these services -
> when you type a URL into a web browser on Mac OS X, the hostname is
> resolved by lookupd. So don't put upper-case characters in any
> hostnames you put in your hyperlinks, or else Mac OS X users won't be
> able to follow them..
> ____________________________________________________________________
> Chris Buxton Men & Mice
> cbuxton@menandmice.com We Make DNS Easy!


It seems like apple is a little unclear about his themselves though.
Acording to this TIL article, netinfo should be consulted first.

In netinfo, I have a record for ti.gbk.com pointing at localhost.

Gbk.com has a wildcard in QDS.

IF I'm connected to the net, I get the real web server.
If I turn off airport, I get localhost. So I know I have it configured
appropriately, because it does work,, BUT it says in the TIL that it's
netinfo, then DNS. Clearly that's not the case. (at least on my
powerbook.)

Additionally, Ti.gbk.com fails completely. I ended up just adding my
powerbook to the local zone.


-- Aaron Lynch
System Administrator
NineWire Digital Solutions || http://ninewire.com

I drive way too fast to worry about cholesterol.




Messages In This Thread:



Return to Digital Point Solutions' Home Page