Assistance with reverse lookup zone

[Kirk]

Frank Pikelner wrote:
> Thank you for everyone's assistance. I have updated the zone files.
> After the updates and restarting BIND, I run "dig +trace ptr
> 170.3.187.64.in-addr.arpa" and the result stops just prior to getting to
> my DNS server and correctly resolving the name of the IP address. I'm
> new to dig and do not know whether this is correct for an RFC2317 zone
> delegation or whether the trace should be completing at my servers and
> resolving the name. My guess is there must be something still incorrect
> on my end. 
> 
> Though, using NSLOOKUP against opendns servers for
> 170.3.187.64.in-addr.arpa does resolve the name correctly.
> 
> 
> NAMED.CONF has the zone defined as follows:
> 
> zone "162-27.3.187.64.in-addr.arpa" IN {
>         type master;
>         file "64_187_3_162-27.rev";
> };
> 
> 
> The zone file looks as follows:
> 
> $ORIGIN .
> $TTL 86400      ; 1 day
> 162-27.3.187.64.in-addr.arpa.   IN SOA  ns1.blue-dot.ca.
> dnsadmin.ns1.blue-dot.ca. (
>                                 2009051202 ; serial
>                                 1800       ; refresh (30 minutes)
>                                 900        ; retry (15 minutes)
>                                 604800     ; expire (1 week)
>                                 1800       ; minimum (30 minutes)
>                                 )
>                         NS      ns1.blue-dot.ca.
>                         NS      ns2.blue-dot.ca.
>                         NS      ns3.blue-dot.ca.
> $ORIGIN 162-27.3.187.64.in-addr.arpa.
> 170                     PTR     smtp3.netcraftcommunications.com.
> 
> 

*Looks like its working to me.*

% dig 170.3.187.64.in-addr.arpa. ptr

; <<>> DiG 9.4.3-P2 <<>> 170.3.187.64.in-addr.arpa. ptr
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1748
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

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

;; ANSWER SECTION:
170.3.187.64.in-addr.arpa. 3941 IN      CNAME   170.162-27.3.187.64.in-addr.arpa.
170.162-27.3.187.64.in-addr.arpa. 86335 IN PTR  smtp3.netcraftcommunications.com.

*Using dig to test at the opendns servers.*

% dig @208.67.222.222 170.3.187.64.in-addr.arpa. ptr

; <<>> DiG 9.4.3-P2 <<>> @208.67.222.222 170.3.187.64.in-addr.arpa. ptr
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 436
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

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

;; ANSWER SECTION:
170.3.187.64.in-addr.arpa. 86400 IN     CNAME   170.162-27.3.187.64.in-addr.arpa.
170.162-27.3.187.64.in-addr.arpa. 86400 IN PTR  smtp3.netcraftcommunications.com.