On Thu, 3 Dec 1998, 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.
It doesn't need to look it up to resolve the address, but many clients
want to do a reverse lookup - turn that IP number into a host name. That
will trigger a DNS lookup if it isn't satisfied in some other way.
In general, real IP applications tend to assume that both forward and
reverse name resolution is more or less readily available. Useful ones
take account of the fact that "available" may involve a significant delay,
but that often takes the form of issuing the request to DNS from a
separate thread or slave process. This protects the app from hanging when
a resolution takes some time (and not all apps feel this is necessary, or
they may be using the reverse lookup as part of their default security or
logging and they don't want to proceed until it completes), but of course
it doesn't help at all with keeping diald from bringing up the link - it
has to do that to query the nameserver.
I hope this isn't too much more than anyone wanted to know about this.
;-)
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
