RFC 2317 question
Mark Andrews
Mark_Andrews at isc.org
Tue Jul 20 23:11:00 UTC 2004
> I'm trying to do in-addr delegation with one of my customers using rfc2317
> using bind 9.2.x. I read the rfc and followed the examples. Here is the
> config on the in-addr zone file:
> ;144/28 RFC 2317 for j2 Global Communications
> ;
> 144-28. IN NS ns2.jfax.com.
> 144-28. IN NS ns.jfax.com.
> ;;
> 144 IN CNAME 144.144-28.81.213.209.in-addr.arpa.
> 145 IN CNAME 145.144-28.81.213.209.in-addr.arpa.
> 146 IN CNAME 146.144-28
> 147 IN CNAME 147.144-28
> 148 IN CNAME 148.144-28
>
> My customer claims my setup is probably not correct, and since this is the
> 1st RFC2317 I have checked and it looks fine to me. His dns servers aren't
> answering any queries and I wonder if that's the problem.
>
> This is what I get with dnsstuff
>
> http://www.dnsstuff.com/tools/ptr.ch?ip=209.213.81.144
>
> Thanks in advance
Remember your customer should want to transfer this zone
as it is required for local reverse lookups to work when
his external link to your servers is down. You might
get some brownie points by recomending that he slave this
zone.
The customer should have something like:
zone "81.213.209.in-addr.arpa" {
type slave;
notify no;
masters { 209.213.64.2; 209.213.72.9; 209.213.80.9; };
file "81.213.209.in-addr.arpa";
};
zone "144-28.81.213.209.in-addr.arpa" {
type master;
file "144-28.81.213.209.in-addr.arpa";
};
Mark
>
> ----------------------------------------------------
> Paul Amaral
> MegaNet Communications
> P: 508 646 0030
> -----------------------------------------------------
>
>
>
> -- Binary/unsupported file stripped by Ecartis --
> -- Type: application/ms-tnef
> -- File: winmail.dat
>
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list