RFC2317 problems

Andreas Papst andreas.papst at univie.ac.at
Mon Apr 3 15:52:40 UTC 2000


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

Hi Ed,

At a first glance this classless in-addr.arpa delegation works fine.
The only problem is that your nameserver ns1.alcpress.com offers
a second NS-RR for 128/28.136.190.206.in-addr.arpa: ns.rjmconsulting.com.
But this should not hurt.

Your problem could be, that your tools do not work properly. That is, they
cannot resolve PTR-records after a CNAME. Try:
dig 129.136.190.206.in-addr.arpa ptr
to obtain good results.

Best regards
ap
________________________________________________________________________
Andreas Papst                      |  E-Mail: andreas.papst at univie.ac.at
                                   |  Phone:
Vienna University Computer Center  |    +43 1 4277 / 140 36
Universitaetsstrasse 7             |  Fax.:
A-1010 Vienna, Austria, Europe     |    +43 1 4277 / 9 140



More information about the bind-users mailing list