Reverse mapping on a non-octet boundary
Sam Pointer
sam.pointer at hpdsoftware.com
Fri Jul 25 10:05:08 UTC 2003
Thanks for your help! I now see that my provider *has* followed the RFC2317
method that I have used before with my other ISP.
I think my confusion came from thinking about it too hard! I now see, as you
say, that I will have to maintain 3 files for the various ranges.
Again, many thanks for your help. This list and its population has been a
wonderful resource to me.
>No, not in this case ( unless your provider makes adjustments )
>
>What your provider delegated is 3 zones :
>0-31.246.167.195.in-addr.arpa.
>32-39.246.167.195.in-addr.arpa.
>40-43.246.167.195.in-addr.arpa.
>
>You will setup 3 zonefiles, ( zone "0-31.246.167.195.in-addr.arpa" { ... )
>with contents exactly as if you owned the 246.167.195.in-addr.arpa :
>@ IN SOA ( ...
> IN NS xxx
> IN NS yyy
>1 IN PTR firsthost.domain.tld.
>2 IN PTR secondhost.domain.tld.
>etc
>If you could convince your provider to delegate all three ranges as :
>hpdsc IN NS ns1.hpdsc.com.
>hpdsc IN NS ns2.hpdsc.com.
>and in their CNAME replace "[0-31|32-39|40-43]" with "hpdsc"
>you would of course be autorative for "hpdsc.246.167.195.in-addr.arpa."
>and could have all your PTR in this file.
This email and any attachments are strictly confidential and are intended
solely for the addressee. If you are not the intended recipient you must
not disclose, forward, copy or take any action in reliance on this message
or its attachments. If you have received this email in error please notify
the sender as soon as possible and delete it from your computer systems.
Any views or opinions presented are solely those of the author and do not
necessarily reflect those of HPD Software Limited or its affiliates.
At present the integrity of email across the internet cannot be guaranteed
and messages sent via this medium are potentially at risk. All liability
is excluded to the extent permitted by law for any claims arising as a re-
sult of the use of this medium to transmit information by or to
HPD Software Limited or its affiliates.
More information about the bind-users
mailing list