Date: Sun, 30 Dec 2001 14:39:50 -0500 From: Bill Moran <wmoran@potentialtech.com> To: Dan Busarow <dan@dpcsys.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: [OT] bind problems Message-ID: <3C2F6D86.8070605@potentialtech.com> References: <Pine.BSF.4.21.0112301054020.97241-100000@java2.dpcsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Busarow wrote:
> On Dec 30, Bill Moran wrote:
>
>>Fernando Gleiser wrote:
>>
>>>Without looking at the named.conf file, we can't say whats wrong with your
>>>bind configuration.
>>>
>>Here it is, with comments snipped out to save space:
>><named.conf>
>>options {
>> directory "/etc/namedb";
>> forward only;
>> forwarders {
>> 192.168.42.252;
>> 151.201.71.129;
>> };
>>};
>>
>
> forward only keeps forces named to use your forwarders for *all*
> queries, including 127.0.0.1
>
> If you leave that option out it will look to itself for zones it
> is a master or slave of.
Hmmm ... well, that makes sense ... in a twisted sort of way. Yet, in
another way, it makes no sense. It just seems like the loopback should
be a special case, somehow.
Is there any accepted way to have 127.0.0.1 resolve while still forcing
the machine to forward all other requests?
Otherwise, I'll just leave it as it is. Having the loopback not resolve
is acceptable if I can keep it relying on its upstream servers for info.
Thanks for the help!
--
Bill Moran
Potential Technology
http://www.potentialtech.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C2F6D86.8070605>