[51189] in North American Network Operators' Group
Re: DNS entries for infrastructure equipment
daemon@ATHENA.MIT.EDU (Stephen Miller)
Wed Aug 21 18:41:02 2002
Date: Wed, 21 Aug 2002 22:39:25 +0000
From: Stephen Miller <steve@smiller.org>
To: jnull <jnelson@jnull.rackspace.com>
Cc: Dan Lockwood <dlockwood@shastalink.k12.ca.us>, nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
--------------040703050608060608030305
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
another way is to use subdomains to separate device, geographic area,
and primary function so that a core router in Washington DC might look
like this:
core-1.wdc.infrastructure.net
this would be a subdomain as well as it would interfaces under it as
well and possibly sub-interfaces. if you're thinking that this could
make the FQDM be quite long...you're right...but one advantage is to be
able to do a "dig axfr" on the sub to see all of the devices in a
specific location such as "dig wdc.infrastructure.net axfr" would return
all of the devices in that geographic location. Then you could dig on a
specific device (as a subdomain) to see all of the interfaces configured
on that device. This can lead to lots of admin overhead but some good
scripts to automate it...it works. of course this is just my opinion.
steve
jnull wrote:
>Dan Lockwood(dlockwood@shastalink.k12.ca.us)@2002.08.21 12:16:20 +0000:
>
>>Does anyone have a resource that has recommendations about how to name
>>interfaces in a DNS name space? Is there a standard that is used? TIA
>>
>>Dan Lockwood
>>
>
>I'm certain there are some good resources available, but f
>m my experience, the most important thing is to work your convention to integrate with you exising or proposed management systems. If your managment system only works from a set domain (i.e. xyz.abc.net--abc being your company and xyz being a subsection) then that label xyz should only have dashes and not periods, otherwise they become a domain themselves.
>
>So, it may depend on the size of your network:
>primary device: r1.company.net
>interface name: pos1-2-r1.company.net
>----or pos1-2.r1.company.net
>----or if you're there is need
>primary device: r1.area-or-function.company.net
>...ect...
>There may be some customization involved with using domain subsets, but using <insert lang> scripts you can parse at either "-" or "." do retrieve information. So, unless size demains creating subsections I would keep the whole name in the top label by using dashes.
>
>
>sig=$header
>
--------------040703050608060608030305
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<html>
<head>
</head>
<body>
another way is to use subdomains to separate device, geographic area, and
primary function so that a core router in Washington DC might look like this:<br>
<br>
core-1.wdc.infrastructure.net<br>
<br>
this would be a subdomain as well as it would interfaces under it as well
and possibly sub-interfaces. if you're thinking that this could make the
FQDM be quite long...you're right...but one advantage is to be able to do
a "dig axfr" on the sub to see all of the devices in a specific location
such as "dig wdc.infrastructure.net axfr" would return all of the devices
in that geographic location. Then you could dig on a specific device (as
a subdomain) to see all of the interfaces configured on that device. This
can lead to lots of admin overhead but some good scripts to automate it...it
works. of course this is just my opinion.<br>
<br>
steve<br>
<br>
jnull wrote:<br>
<blockquote type="cite" cite="mid:20020821194057.GA29612@jnull.rackspace.com">
<pre wrap="">Dan Lockwood(<a class="moz-txt-link-abbreviated" href="mailto:dlockwood@shastalink.k12.ca.us">dloc<a class="moz-txt-link-abbreviated" href="mailto:dlockwood@shastalink.k12.ca.us)@2002.08.21">dlockwood@shastalink.k12.ca.us)@2002.08.21</a> 12:16:20 +0000:<br></pre>
<blockquote type="cite">
<pre wrap="">Does anyone have a resource that has recommendations about how to name<br>interfaces in a DNS name space? Is there a standard that is used? TIA<br> <br>Dan Lockwood<br></pre>
</blockquote>
<pre wrap=""><!----><br>I'm certain there are some good resources available, but f<br>m my experience, the most important thing is to work your convention to integrate with you exising or proposed management systems. If your managment system only works from a set domain (i.e. xyz.abc.net--abc being your company and xyz being a subsection) then that label xyz should only have dashes and not periods, otherwise they become a domain themselves.<br><br>So, it may depend on the size of your network:<br>primary device: r1.company.net<br>interface name: pos1-2-r1.company.net<br>----or pos1-2.r1.company.net <br>----or if you're there is need<br>primary device: r1.area-or-function.company.net<br>...ect...<br>There may be some customization involved with using domain subsets, but using <insert lang> scripts you can parse at either "-" or "." do retrieve information. So, unless size demains creating subsections I would keep the whole name in the top label by using dashes.<br><
br><br>sig=$header<br></pre>
</blockquote>
<br>
</body>
</html>
--------------040703050608060608030305--
