DNS PTR Records subnet

[Conor Daly]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

RFC 2317 details how to (should) perform reverse delegation at the
customer and provider level and should give some info on how to create
your zones here.

ftp://ftp.rfc-editor.org/in-notes/bcp/bcp20.txt

Conor

NOC Lead
IE Domain Registry

web: www.iedr.ie
tel: +35312365400
fax: +35312300365
skype: conorpdaly


Joseph S D Yao wrote:
> On Thu, Mar 15, 2007 at 01:34:24PM -0400, Sangoi, Nehal (GE Supply, consultant) wrote:
>> Hi
>>  
>> How can I define my reverse record zone files for the subnet like
>> "3.160.232.0/22"
>>  
>> should it be "160.3.in-addr.arpa"
>>  
>> or should it be like 
>> "235.160.3.in-addr.arpa"
>> "234.160.3.in-addr.arpa"
>> "232.160.3.in-addr.arpa"
> 
> 
> Do you own the 3.160.0.0/16 network?  No, you do not (at least, not from
> what you said above).  Therefore you must not define a reverse DNS zone
> for it.
> 
> You must define zones for those networks that you do own.  As you almost
> say, the zones you would define are:
> 	232.160.3.in-addr.arpa
> 	233.160.3.in-addr.arpa
> 	234.160.3.in-addr.arpa
> 	235.160.3.in-addr.arpa
> 
> You must then ask the person who DOES serve 160.3.in-addr.arpa to
> delegate those subdomains to your name servers.  Otherwise, nobody will
> be able to see your zones!
> 
> Authoritative answers can be found from:
> 3.in-addr.arpa
> 	origin = ns.ge.com
> 	mail addr = hostmaster.ge.com
> 	serial = 2006102301
> 	refresh = 10800
> 	retry = 3600
> 	expire = 604800
> 	minimum = 300
> 
> OK, it looks like your 3.in-addr.arpa hostmaster likes to keep all his
> networks in one big file.  So, you have to ask him or her to delegate
> 232.160, 233.160, 234.160, and 235.160 to your name servers.
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF+qVICV8Py+3MmrsRAn64AKC0MzMv9OkB+5KtEIX5aHR8wk6MRwCggKco
NHr+vEwvUJGvUggBuIqfdfY=
=yar0
-----END PGP SIGNATURE-----