Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!ucbvax!naggum.uu.no!erik
From: erik@naggum.uu.no (Erik Naggum)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: HINFO record consistency
Message-ID: <1990-333-78765@uunic.uu.no>
Date: 30 Nov 90 21:52:45 GMT
References: <9011301955.AA11368@intrepid.erg.sri.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 21

> Well, this sounded like an interesting idea, so I went and FTPed the RFC,
> and installed all the stuff in my name server.  I have the following info
> now for domain erg.sri.com, from a "dig erg.sri.com any" request:

[ whole bunch of records deleted ]

I think you missed a small point in RFC 1101.  The idea is to make one
PTR RR for ERG.SRI.COM pointing at your class B network, and vice
versa, but NOT to point to all subnets.  These would have their own
IN-ADDR.ARPA PTR RRs pointing at the proper network name, such as
ERG-SN-1.ERG.SRI.COM for subnet 1.  With the aid of the A RRs for the
network number, you can find those subnets easy enough, anyway.

That is, the PTR RR should be:

erg.sri.com.    86400   PTR     0.0.18.128.in-addr.arpa.

You now have significantly less data to stuff into the reply packet,
and I believe the problems you experience will go away.  :-)

[Erik]