Only one reverse lookup works
Mark Andrews
Mark_Andrews at isc.org
Thu Dec 16 21:28:20 UTC 2004
> In trying to set up a reverse zone file for address block
> 64.161.5.105 to 64.161.5.110 only one address seems to resolve
> successfully: 64.161.5.105 resolves to www.zefox.com, which is
> correct.
>
> The primary nameserver is at 64.161.5.108, with a named.conf file of
>
> options {
> directory "/etc/namedb";
> pid-file "/var/run/named/pid";
>
> };
>
>
> zone "." {
> type hint;
> file "named.root";
> };
>
> zone "0.0.127.IN-ADDR.ARPA" {
> type master;
> file "localhost.rev";
> };
>
> zone "1.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-v6.rev";
> };
>
>
> /*zone "0.168.192.in-addr.arpa" {
> type slave;
> file "s/0.168.192.in-addr.arpa.bak";
> masters {
> 192.168.1.4;
> };
> */
> zone "105.5.161.64.in-addr.arpa" {
> type master;
> file "64.161.5.105.rev";
> };
>
> zone "zefox.com" {
> type master;
> file "hosts.zefox.com";
> };
> zone "zefox.org" {
> type master;
> file "hosts.zefox.org";
> };
> zone "zefox.net" {
> type master;
> file "hosts.zefox.net";
> };
>
> The relevant inverse zone is 105.5.161.64.in-arpa.,
> which is described in:
>
> $TTL 86400
> ;
> ; Address to hostname mappings for all the *zefox* hosts
> ;
> 105.5.161.64.in-addr.arpa. IN SOA ns1.zefox.net root.ns1.zefo
> x.net. (
> 2004121504 ; serial
> 21600 ; refresh
> 1800 ; retry
> 604800 ; expire
> 900 ) ; negative cache ttl
> IN NS ns1.zefox.net.
> IN NS ns2.zefox.net.
>
> 108.5.161.64.in-addr.arpa. IN NS ns1.zefox.net.
> 109.5.161.64.in-addr.arpa. IN NS ns2.zefox.net.
> 105.5.161.64.in-addr.arpa. IN PTR www.zefox.com.
> 106.5.161.64.in-addr.arpa. IN PTR www.zefox.net.
> 107.5.161.64.in-addr.arpa. IN PTR www.zefox.org.
> 108.5.161.64.in-addr.arpa. IN PTR ns1.zefox.net.
> 109.5.161.64.in-addr.arpa. IN PTR ns2.zefox.net.
> 110.5.161.64.in-addr.arpa. IN PTR gateway.zefox.net.
From the parent zone.
110.5.161.64.in-addr.arpa. 7200 IN CNAME 110.104.5.161.64.in-addr.arpa.
104.5.161.64.in-addr.arpa. 7200 IN NS ns1.zefox.net.
104.5.161.64.in-addr.arpa. 7200 IN NS ns2.zefox.net.
104.5.161.64.in-addr.arpa. 7200 IN NS ns1.pbi.net.
104.5.161.64.in-addr.arpa. 7200 IN NS ns2.pbi.net.
;; Received 182 bytes from 206.13.29.11#53(ns2.pbi.net) in 725 ms
Firstly the zone should be 104.5.161.64.in-addr.arpa not
105.5.161.64.in-addr.arpa. The names should all be at or *below*
104.5.161.64.in-addr.arpa.
$ORIGIN 104.5.161.64.in-addr.arpa.
$TTL 3600
@ SOA ns1.zefox.net. root.ns1.zefox.net. (
2004121700 21600 1800 604800 900 )
@ NS ns1.zefox.net.
@ NS ns2.zefox.net.
@ NS ns1.pbi.net.
@ NS ns2.pbi.net.
105 PTR www.zefox.com.
106 PTR www.zefox.net.
107 PTR www.zefox.org.
108 PTR ns1.zefox.net.
109 PTR ns2.zefox.net.
110 PTR gateway.zefox.net.
Secondly you should be a stealth slave for the parent zone.
This will allow local lookups to work when you can't reach
the parent servers.
zone "5.161.64.in-addr.arpa" {
type slave;
masters { 206.13.28.11; 206.13.29.11; };
file "64.161.5.rev";
notify no;
};
> The reverse zone loads without errors on ns1.zefox.net at
> 64.161.5.108 using named 8.3.7-REL Mon Feb 23 18:30:22 GMT 2004
> but can resolve (locally) only address 64.161.5.105, all others
> result in a "servfail" reply.
>
> Remote queries fail on inability to reverse resolve the namesever
> address, which is consistent with other failures 8-)
>
> Seems like this is an error in the 105.5.161.64.in-arpa zone file,
> but I surely can't see it. Any help much appreciated!
>
> Thanks to all with the patience to read this far!
>
> bob prohaska
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list