PTR delgation confused

[Kevin Darcy]

One obvious configuration problem: your SOA record doesn't match the
name of the zone. The zone is loaded as 141.36.208.in-addr.arpa, but the
SOA record is -- because of the $ORIGIN directive -- interpreted as
being for 224/28.141.36.208.in-addr.arpa.

You could certainly set up your machine as master for
141.36.208.in-addr.arpa zone, but unless you are the *real* master of
the zone, i.e. unless the zone is properly delegated to you, the rest of
the Internet will not be able to resolve the reverse records contained
within it. Your provider (Concentric?) is almost certainly the real
master of the zone. The zone file on the real master is where your PTRs
need to be added, or, following RFC 2317's "classless in-addr.arpa
delegation", the place where CNAMEs need to be added, pointing to PTRs
in a zone which is delegated to your server(s).


- Kevin

Henny L wrote:

> Hello,
> I was given 16 IPs from my ISP. I have setup  named and it's working
> fine, but the problem is i
> don't think i have configure PTR correctly. My IPs are
> 208.36.141.224-38/28
> Could someone point out my mistake(s).  };
> named.conf :
>
> zone "141.36.208.in-addr.arpa" {
>         type master;
>         file "mydomain.rev";
> };
>
> here is the PTR file
> $ORIGIN 224/28.141.36.208.in-addr.arpa.
> @       IN      SOA     test.mydomain.org. hostmaster.mydomain.org. (
>                             2000107  ; Serial
>                             3600     ; Refresh
>                             9600     ; Retry
>                             360000   ; Expire
>                             3600 )    ; Minimum TTL
>
>         IN      NS      ns.mydomain.org.
>         IN      NS      ns2.mydomain.org.
>
> 226     IN      PTR     mydomain.org
> 227     IN      PTR     mydomain2.org.
>
> thanks in advance