Problem with reverse lookup in CIDR delegated domain [file details]

[Jim]

(first time configuring bind/dns)

I am setting up a domain in a block of 5 IP numbers:
   67.116.182.186 - 67.116.182.190  hostmask 255.255.255.248

with network access of 67.116.182.184/29

I have set the domain up in bind 9.2.2 and everything is
working except reverse, i.e. number to name.

Below are the files: named.conf and the forward and reverse
zone files for the domain.

FILE = /etc/named.conf

options {
	directory "/var/named";
	query-source address * port 53;
	pid-file "named.pid";
};

[root, local & localrev zones not listed for brevity]

zone "jms-corp.net" {
	type master;
	file "m/named.jms-corp.net";
	notify yes;
};

zone "182.116.67.in-addr.arpa" {
	type master;
	file "m/named.67.116.182";
	notify yes;
};


FILE = /var/named/m/named.jms-corp.net

$TTL	86400
@       IN      SOA     dragon.jms-corp.net. jrs.jms-corp.net.  (
                                      2          ; Serial
                                      8H         ; Refresh
                                      10M        ; Retry
                                      3600000    ; Expire
                                      86400 )    ; Minimum

        IN      NS      ns.jms-corp.net.
        IN      NS      ns1.pbi.net.
        IN      MX      10 jms-corp.net.
        IN      A       67.116.182.186

localhost  IN   A       127.0.0.1

ns      IN      A       67.116.182.186
www     IN      A       67.116.182.186
ftp     IN      A       67.116.182.186
mail    IN      A       67.116.182.186


FILE = /var/named/m/named.67.116.182

$TTL	86400
@       IN      SOA     dragon.jms-corp.net. jrs.jms-corp.net.  (
                                      5          ; Serial
                                      8H         ; Refresh
                                      10M        ; Retry
                                      3600000    ; Expire
                                      86400 )    ; Minimum
; My nameserver
        IN      NS      ns.jms-corp.net.
; Secondary nameserver from pacbell
        IN      NS      ns1.pbi.net.

186.184.182.116.67.in-addr.arpa.     IN      PTR     dragon.jms-corp.net.

==============================

Note the above PTR record. This is what I was told was needed here.
When I read RFC2317 there was nothing like this. I did find at the
following URL a slight explanation:

   http://www.acmebw.com/askmrdns/00007.htm

Following is the output of dig using the ISPs nameserver:

; <<>> DiG 9.2.2-P3 <<>> @ns1.pbi.net -x 67.116.182.186
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42182
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 2

;; QUESTION SECTION:
;186.182.116.67.in-addr.arpa.	IN	PTR

;; ANSWER SECTION:
186.182.116.67.in-addr.arpa. 7200 IN	CNAME	186.184.182.116.67.in-addr.arpa.

;; AUTHORITY SECTION:
184.182.116.67.in-addr.arpa. 7200 IN	NS	dragon.jms-corp.net.
184.182.116.67.in-addr.arpa. 7200 IN	NS	ns1.pbi.net.
184.182.116.67.in-addr.arpa. 7200 IN	NS	ns2.pbi.net.

;; ADDITIONAL SECTION:
ns1.pbi.net.		172800	IN	A	206.13.28.11
ns2.pbi.net.		172800	IN	A	206.13.29.11

;; Query time: 33 msec
;; SERVER: 206.13.28.11#53(ns1.pbi.net)
;; WHEN: Wed Mar  3 09:40:23 2004
;; MSG SIZE  rcvd: 172

Which shows the "extended" CNAME record. Next is the output of dig
from my nameserver:

; <<>> DiG 9.2.2-P3 <<>> -x 67.116.182.186
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13644
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;186.182.116.67.in-addr.arpa.	IN	PTR

;; AUTHORITY SECTION:
182.116.67.in-addr.arpa. 86400	IN	SOA	dragon.jms-corp.net. jrs.jms-corp.net. 5 28800 600 3600000 86400

;; Query time: 1 msec
;; SERVER: 67.116.182.186#53(67.116.182.186)
;; WHEN: Wed Mar  3 09:42:19 2004
;; MSG SIZE  rcvd: 104

Anyone have any help, comments, dumbsh*ts, etc to offer?

Thank you

Jim

jrs (at) jms-corp.net | j-m-s (at) pacbell.net
-- 

Quidquid latine dictum sit, altum viditur.