RFC2317 problems

[Matt Marshall]

It appears to be working correctly...

mmars at myhost[684]% dig -x 206.190.136.130 ptr

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

;; ANSWERS:
130.136.190.206.in-addr.arpa.   86393   CNAME   130.128/28.136.190.206.in-addr.arpa.
130.128/28.136.190.206.in-addr.arpa.    86393   PTR     igor.alcpress.com.

;; AUTHORITY RECORDS:
128/28.136.190.206.in-addr.arpa.        86393   NS      ns1.alcpress.com.

;; ADDITIONAL RECORDS:
ns1.alcpress.com.       87650   A       206.190.136.130

;; Total query time: 9 msec
;; FROM: myhost to SERVER: default -- 4.2.2.1
;; WHEN: Mon Apr  3 15:23:33 2000
;; MSG SIZE  sent: 46  rcvd: 160

mmars at myhost[685]% 

--Matt 

Matt Marshall
GTE Internetworking Powered By BBN



On Mon, Apr 03, 2000 at 08:02:35AM -0700, Ed Sawicki wrote:
> My ISP has delegated reverse dns for my subnet (206.190.136.128/28)
> to me. They told me to create a "128/28.136.190.206.in-addr.arpa"
> zone. I think I've done that with this entry in my named.conf file.
> 
> zone "128/28.136.190.206.in-addr.arpa" {
>      type master;
>      file "206.190.136"
> };
> 
> The 206.190.136 file contains the following.
> 
> $TTL 86400
> $ORIGIN 128/28.136.190.206.in-addr.arpa.
> @	IN	SOA	ns1.alcpress.com. hostmaster.alcpress.com.
>                        (2000032701 86400 3600 345600 86400)
> @	IN	ns	ns1.alcpress.com.
> 129	IN	PTR	ed.alcpress.com.
> 130	IN	PTR	igor.alcpress.com.
> 131	IN	PTR	ns.alcpress.com.
> <snip>
> 142	IN	PTR	bay.alcpress.com.
> 
> This is not working properly. It's not clear to me whether I
> should be able to query my dns server directly so my
> troubleshooting abilities are a bit limited. I've read RFC2317
> over and over. Is the problem on my side or on my ISP's side?
> 
> Ed Sawicki
> 
>