reverse problem

[David Kirk]

> hiya, i'm fairly new to the list and i was wondering if anyone could help me
> with a problem i'm having with reverse lookups for a c-class
>
> our nameservers are ns1.pwebtech.com and ns2.pwebtech.com and the block is
> 64.21.139
>
> for some reason the block just will not reverse and i've checked everything i
> can think of. all our files appear correct, and our upstream (ns1.nac.net)
> assures us that all is delegated correctly
>
> any ideas?
>
> thanks in advance,
> Dave

Are you supposed to be authoritative for the reverse for the entire /24
network 64.21.139.0/24?  If so, it appears that the reverse for that
block (139.21.64.in-addr.arpa) is not delegated to your name servers,
as your upstream has suggested ...

# dig 139.21.64.in-addr.arpa NS

; <<>> DiG 2.2 <<>> 139.21.64.in-addr.arpa NS
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; Ques: 1, Ans: 2, Auth: 0, Addit: 2
;; QUESTIONS:
;;      139.21.64.in-addr.arpa, type = NS, class = IN

;; ANSWERS:
139.21.64.in-addr.arpa. 66636   NS      NS2.NAC.NET.
139.21.64.in-addr.arpa. 66636   NS      NS1.NAC.NET.

;; ADDITIONAL RECORDS:
NS2.NAC.NET.    149846  A       207.99.0.2
NS1.NAC.NET.    149846  A       207.99.0.1

;; Total query time: 4 msec
;; FROM: <> to SERVER: default -- <>
;; WHEN: Fri Aug 24 02:17:19 2001
;; MSG SIZE  sent: 40  rcvd: 115

... it is delegated to their name servers.  The NAC.NET name servers
state that the pwebtech name servers are the NS hosts for this zone ...

#  dig @NS1.NAC.NET 139.21.64.in-addr.arpa NS

; <<>> DiG 2.2 <<>> @NS1.NAC.NET 139.21.64.in-addr.arpa NS
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 2, Auth: 0, Addit: 2
;; QUESTIONS:
;;      139.21.64.in-addr.arpa, type = NS, class = IN

;; ANSWERS:
139.21.64.in-addr.arpa. 3600    NS      ns2.pwebtech.com.
139.21.64.in-addr.arpa. 3600    NS      ns1.pwebtech.com.

;; ADDITIONAL RECORDS:
ns2.pwebtech.com.       170834  A       209.123.159.1
ns1.pwebtech.com.       170834  A       209.123.167.10

;; Total query time: 16 msec
;; FROM: <> to SERVER: NS1.NAC.NET  207.99.0.1
;; WHEN: Fri Aug 24 02:19:38 2001
;; MSG SIZE  sent: 40  rcvd: 120

... and a query of the pwebtech servers hands out NS records
pointing back to the NAC.NET name servers ...

# dig @ns2.pwebtech.com 139.21.64.in-addr.arpa NS

; <<>> DiG 2.2 <<>> @ns2.pwebtech.com 139.21.64.in-addr.arpa NS
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 2, Auth: 0, Addit: 2
;; QUESTIONS:
;;      139.21.64.in-addr.arpa, type = NS, class = IN

;; ANSWERS:
139.21.64.in-addr.arpa. 44346   NS      NS1.NAC.NET.
139.21.64.in-addr.arpa. 44346   NS      NS2.NAC.NET.

;; ADDITIONAL RECORDS:
NS1.NAC.NET.    100269  A       207.99.0.1
NS2.NAC.NET.    151904  A       207.99.0.2

;; Total query time: 19 msec
;; FROM: <> to SERVER: ns2.pwebtech.com  209.123.59.1
;; WHEN: Fri Aug 24 02:24:01 2001
;; MSG SIZE  sent: 40  rcvd: 115

If the pwebtech.com name servers should be serving this reverse
zone, then the zone should be delegated directly to the pwebtech
servers, and avoid all of the circular behavior that appears to be
happening as a result of the current setup.

Thanks,

dave