Date: Sun, 30 Dec 2001 11:09:09 -0500 From: Bill Moran <wmoran@potentialtech.com> To: Fernando Gleiser <fgleiser@cactus.fi.uba.ar> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: [OT] bind problems Message-ID: <3C2F3C25.8090601@potentialtech.com> References: <20011230105415.P50812-100000@cactus.fi.uba.ar>
next in thread | previous in thread | raw e-mail | index | archive | help
Fernando Gleiser wrote:
> On Sat, 29 Dec 2001, Bill Moran wrote:
>>
>>I've attempted to configure named to "forward only" so that it just does all
>>its resolving through the upstream servers. I also have the clients
>>configured to use the upstream servers as backups. Apparently this caching
>>server is never answering any queries and the upstreams are getting all
>>the questions (which, obviously, defeats the purpose)
>>
>
> 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;
};
};
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" {
type master;
file "localhost.rev";
};
</named.conf>
>>When I run nslookup on the proxy, I get an error:
>>*** Can't find server name for address 127.0.0.1: No response from server
>>And it falls back to the secondary to answer the queries.
>>
>
> Don't use nslookup. Again: Don't use nslookup. Use dig instead. nslookup
> fails miserably if you don't have the reverse zones properly configured.
> It tries a reverse lookup of the IP listed in the "nameserver" clause of
> resolv.conf and dies if fails.
I'd assume that nslookup also does not check the /etc/hosts file for this
information either, because it's there. (as Dan Busarow suggested) and has
been there all along.
The good news is that while fooling with dig I found that the computer was
indeed answering queries. The only query it seems unable to answer is
1.0.0.127.IN-ADDR.ARPA.
Here's my localhost.rev - anyone see any clues as to the problem here?
<localhost.rev>
$TTL
3600
@
IN
SOA
nhproxy.redstone.nh. jimg.redstonehighlands.org. (
20011018 ; Serial
3600 ; Refresh
900 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS nhproxy.redstone.nh.
1
IN
PTR
localhost.redstone.nh.
</localhost.rev>
> I don't know why someone wrote a debugging tool for DNS which needs named
> properly configured in the first place.
Can't argue with you there. That doesn't make much sense.
--
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?3C2F3C25.8090601>