From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] dns ptr records. From: Tim Wiess Date: Mon, 8 Oct 2007 09:01:08 -0700 In-Reply-To: <44b4a85f8bea97dbbd445beac09db84a@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: cce71128-ead2-11e9-9d60-3106f5b1d025 delayed response, but thanks for letting everyone know.... > thanks to geoff for pointing me in the correct direction. > > the rfc in question is rfc 2317. i'll outline what's required, > since it wasn't obvious to me. > > here's an example setting up t2317 ptr records for 65.14.39.130 and > 65.14.39.131 in the network 64.14.39.128/123. > > # first we have to have the correct ipnet setup. > # dns needs this information to find the netmask. > > ipnet=coraidt1 ip=65.14.39.128 ipmask=/123 > # other stuff you may need goes here. > > # next we need to declare our dom. dns normally does this > # for us, but for 2317-style reverse lookups, we do it ourselves. > > dom=128.39.14.65.in-addr.arpa soa= > refresh=3600 ttl=3600 > ns=ns1.coraid.com > ns=ns2.coraid.com > > # and the entries. > dom=130.128.39.14.65.in-addr.arpa > dom=131.128.39.14.65.in-addr.arpa > > - erik