RFC 2317 question

[Kevin Darcy]

Neither ns.jfax.com or ns2.jfax.com appear to have any knowledge of the
144-28.81.213.209.in-addr.arpa zone.

Perhaps there was a miscommunication over what the name of the zone would be?


- Kevin

P.S. This is yet another reason why I advocate, departing from RFC 2317
somewhat, putting the PTR records in "forward" zones. There is generally far
less zone-naming confusion over those.

"MegaNet DomainReg." wrote:

> Im delegating a /28 for a customer using rfc 2317.
>
> example in-addr zone file for 81.213.209.in-addr.arpa:
> $TTL 86400
> @ IN SOA reuben.meganet.net. sysadmin.cerise.meganet.net. (
>                 2002013010      ;serial
>                 10800           ;refresh 3hrs
>                 3600            ;retry 1hr
>                 604800  ;expire 1 wk
>                 86400 ) ;min TTL 1 day
>         IN NS   ns1.bos.ma.meganet.net.
>         IN NS   ns1.prv.ri.meganet.net.
>         IN NS   reuben.meganet.net.
> ;
> ;
> ;
> 44-28  IN NS   ns2.jfax.com.
> 144-28  IN NS   ns.jfax.com.
> ;;
> 144     IN CNAME 144.144-28
> 145     IN CNAME 145.144-28
> 146     IN CNAME 146.144-28
>
> the customer seems to have all the PTR RR's setup on his end however i can't
> seem to be able to do a reverse lookup on his /28.
>
> any ideas would be great, thanks
>
> ----------------------------
> Paul Amaral
> MegaNet Communications
> 508-646-0030
> ----------------------------