RFC 2317 question

Barry Margolin barmar at genuity.net
Wed Jan 30 18:57:40 UTC 2002


In article <a398st$40b at pub3.rc.vix.com>,
MegaNet DomainReg. <pamaral at corp.meganet.net> 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.

There's a typo there, it should be 144-28.

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

ns2.jfax.com is configured as an authoritative server for
81.213.209.in-addr.arpa, not the subdomain you delegated to it:

% dig -x 209.213.81.144-28 soa @ns2.jfax.com +norec

; <<>> DiG 8.3 <<>> -x soa @ns2.jfax.com +norec 
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35771
;; flags: qr aa ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;;	144-28.81.213.209.in-addr.arpa, type = SOA, class = IN

;; AUTHORITY SECTION:
81.213.209.in-addr.arpa.  1D IN SOA  ns2.jfax.com. dns-admin.ns2.jfax.com. (
					13		; serial
					3H		; refresh
					30M		; retry
					1W		; expiry
					1D )		; minimum

And ns.jfax.com isn't authoritative for either domain:

% dig -x 209.213.81.144-28 soa @ns.jfax.com +norec

; <<>> DiG 8.3 <<>> -x soa @ns.jfax.com +norec 
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22948
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 10
;; QUERY SECTION:
;;	144-28.81.213.209.in-addr.arpa, type = SOA, class = IN

;; AUTHORITY SECTION:
209.in-addr.arpa.	7h34m11s IN NS	ARROWROOT.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	BUCHU.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	CHIA.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	DILL.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	EPAZOTE.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	FIGWORT.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	GINSENG.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	HENNA.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	INDIGO.ARIN.NET.
209.in-addr.arpa.	7h34m11s IN NS	JERK.ARIN.NET.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list