[97439] in North American Network Operators' Group
Re: Thoughts on best practice for naming router infrastructure in DNS
daemon@ATHENA.MIT.EDU (K K)
Thu Jun 14 16:26:46 2007
Date: Thu, 14 Jun 2007 15:25:52 -0500
From: "K K" <kkadow@gmail.com>
To: nanog@nanog.org
In-Reply-To: <daf895880706140956r24cb09c9xc6764bad416821f@mail.gmail.com>
Errors-To: owner-nanog@merit.edu
On 6/14/07, randal k <nanog@data102.com> wrote:
> This particular issue has been confounding to work around as well. The issue
> of constantly updating DNS to match the current topology is a pain, but in
> my opinion, very necessary.
I'm not entirely convinced DNS records for every possible interface
address are needed, in part because it's so difficult to keep them
updated with topology changes over time.
I think the first step is to choose a standard subdomain for
infrastructure, like "wan.example.net". The next step (the last step
in many companies) is to populate forward and reverse DNS for the
"source interface" and managed IP of each device, so you can at least
resolve the IP which the router will use when sending traps, NTP,
TACACS+ and other requests, and to keep the NMS sane.
Kevin
