[112855] in North American Network Operators' Group
Re: REVERSE DNS Practices.
daemon@ATHENA.MIT.EDU (Tom Wright)
Sun Mar 22 20:03:54 2009
From: Tom Wright <twright@internode.com.au>
To: bmanning@vacation.karoshi.com
In-Reply-To: <20090321130055.GA5782@vacation.karoshi.com.>
Date: Mon, 23 Mar 2009 10:31:22 +1030
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On 21/03/2009, at 11:30 PM, bmanning@vacation.karoshi.com wrote:
> if you really don't care about the actual node, then you should map
> the
> numbers to topologically significant names - after all, the reverse
> map
> follows topology, not some goofball - layer 9 - ego trip thing.
Agreed - and its certainly manageable if you automate the process.
Generating reverse lookups from your config backups is a pretty
reliable way of doing this for infrastructure/dynamic allocations.
Your NOC staff will love it because they won't have to worry
when they shuffle around local pools, or turn up new interfaces.
> or - the more modern approach is to let the node (w/ proper
> authorization)
> do a secure dynamic update of the revserse map - so the forward and
> reverse
> delegations match. ... a -VERY- useful technique.
Are there any network operators actually doing this on a large scale?
-- Tom
--
Kind Regards,
Tom Wright
Internode Network Operations
P: +61 8 8228 2999
W: http://www.internode.on.net
