Hey,
I solved this problem too, by setting up named with 4 zones, the localhost zone,
The local domain zone, a reverse lookup zone for the local domain (THIS ONE IS
IMPORTANT) and of course, the root servers zone. While not as simple as the hosts file
fix, I think it's a bit more elegant.
Kenneth P. Persing
-----Original Message-----
From: Martin J. Maney [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, December 03, 1998 8:35 AM
To: Bill Perpelitt
Cc: Paolo Sommaruga; [EMAIL PROTECTED]
Subject: Re: diald and local net
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.
A number of things may not work without having a way to resolve, and
perhaps even to reverse resolve, your local machines'names and IP
addresses, so setting this up is a good idea even if you aren't using
diald.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
