North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Thoughts on best practice for naming router infrastructure in DNS

  • From: K K
  • Date: Thu Jun 14 16:28:07 2007
  • Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Mh3KSC4Z0XHWatZhfxCF3503NxzyIFq4xoRzXx5saBYGmGnibuaxo24UVHx9os17+S+lZy3ldz2lPg3URLUAzgSnBv1/bJyHYrMq5FpR3PWuXVg23cd9WdclVxI27/mowsIF/rkHrWz2ApLzScZxyLiLFvOTCgA1OS3hGyWDMrs=
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CWoNVg+N/MeR4Pr8JOlaxrPNOjklNjfBd9ZYqs6RO4sLk0qF6k+sbaIrqXuXkKl8soXIsRGtUxQ+OIOeAri53ZuQQrzyrKK0RzUzEObziE2PjBgRrE8iiCsZSlVU3v8M+qJshwL4a1zp1EPSilj3O9Obk4RtIJkOLoXLn8chp2Q=

On 6/14/07, randal k <[email protected]> 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