Bill Perpelitt wrote:
>
> Well -- what seemed odd to me was that I was using 192.168.0.40
> as a client address, and I figured it would automatically see this as
> a local address and not attempt to do a DNS lookup. I finally gave
> in and added the ip address to the hosts file.
Welcome to Windows 95. Like some broken rsh versions, it does hostname
lookups on IP numbers, just to be sure. After all, the user would never
type in an actual numeric address, right?
Ed
>> On Wed, 2 Dec 1998, Bill Perpelitt wrote:
>>
>>> I had a similar problem. I'm sure there's a more graceful answer
>>> than the one I've come up with, but I just added the ip addresses of
>>> my clients (just a few, fortunately) to the /etc/hosts file.
>>>
>>> My system was connecting to my isp everytime there was a DNS
>>> request, even if the address was local to my network. The above fix
>>> handled it. There's probably a smarter way to get this to work, but
>>> for a few stations, the above worked for me.
>>
>> No, that's the simplest way to fix that problem. If you need to resolve
>> local host addresses, there has to be a local way of looking them up -
>> otherwise the resolver will attempt to query the real nameserver, bringing
>> up the link just to be told (unless you used a name that does exist out
>> there, whcih will cause other difficulties) that nope, this name is
>> unknown.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
