9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Wiess <tim@nop.cx>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dns ptr records.
Date: Mon,  8 Oct 2007 09:01:08 -0700	[thread overview]
Message-ID: <eb79577b34ca3f4ff0967ab1f18ff5c7@akira.nop.cx> (raw)
In-Reply-To: <44b4a85f8bea97dbbd445beac09db84a@quanstro.net>

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



  reply	other threads:[~2007-10-08 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <af3fc62915bf50a173c92679ba0d36b3@plan9.bell-labs.com>
2007-10-05 17:27 ` erik quanstrom
2007-10-08 16:01   ` Tim Wiess [this message]
2007-10-08 17:28     ` erik quanstrom
2007-10-05 18:17 erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2007-10-04 21:27 erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb79577b34ca3f4ff0967ab1f18ff5c7@akira.nop.cx \
    --to=tim@nop.cx \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).