Only one reverse lookup works

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.zefox.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.



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