Alex Zbyslaw <[EMAIL PROTECTED]> writes:
> Gary W. Swearingen wrote:
>
>>Mozilla apparently doesn't even use my local DNS as it still hangs.
>>(I must admit that I've never checked my caching DNS's cache.)
>>
>>
> Mozilla will use resolve.conf, if it is there. It will also cache answers
> for a
Gary W. Swearingen wrote:
Now "host", "dig", and "nslookup" work OK, even without an
/etc/resolv.conf file. But sendmail seems to need the later.
(It just has "nameserver 127.0.0.1".)
[...]
Mozilla apparently doesn't even use my local DNS as it still hangs.
(I must admit that I've never check
Chuck Swiger <[EMAIL PROTECTED]> writes:
> Note that the resolver will treat lookups of "localhost." and "localhost"
> differently if you have a domain or search
> directive specified in /etc/resolv.conf. You could and perhaps should ensure
> that the one ending in a period exists in
> a zone f
Gary W. Swearingen wrote:
[ ... ]
so I'd think domain resolution should look in /etc/hosts before
even checking my cache-only named. Which it seems to do for "ping",
but not for "host", "nslookup", or "mozilla".
As Lowell noted, programs like "nslookup" and "dig" are designed to query DNS
spe
Lowell Gilbert <[EMAIL PROTECTED]> writes:
> Of course it won't work for nslookup(1); it's not supposed to.
> nslookup is specifically intended for querying a name server. The
> documentation for host(1) isn't as clear on the subject, but my
> reading of it seems to indicate the same thing.
Well
[EMAIL PROTECTED] (Gary W. Swearingen) writes:
> Kevin Kinsey <[EMAIL PROTECTED]> writes:
>
> > Did you `sh /var/named/etc/namedb/make-localhost` ?
>
> Yup, but that only handles the reverse translation (which works OK)
> and, of course, doesn't handle other stuff I might have in "/etc/hosts".
>
Kevin Kinsey <[EMAIL PROTECTED]> writes:
> Did you `sh /var/named/etc/namedb/make-localhost` ?
Yup, but that only handles the reverse translation (which works OK)
and, of course, doesn't handle other stuff I might have in "/etc/hosts".
I also have in /etc/nsswitch.conf:
hosts: files dns
so
Gary W. Swearingen wrote:
I think I followed the bind manual and poked around /var/named and it
has been working OK for a few weeks until I pointed my browser to
"localhost" and then I tried "host localhost". It can resolve
"127.0.0.1" back to "localhost.localhost." fine, but if I try
my name "l
I think I followed the bind manual and poked around /var/named and it
has been working OK for a few weeks until I pointed my browser to
"localhost" and then I tried "host localhost". It can resolve
"127.0.0.1" back to "localhost.localhost." fine, but if I try
my name "localhost" or "localhost.local
