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

I remember in the past an excellent system using Sesame Street characters names.

I've done things like this, but I confine it to my workstations. My network devices and production systems follow a pretty straightforward naming system.

Workstations in past lives have been:
Addams Family characers (lurch, gomez, pugsley...)
Guitar effects (whammy, distortion, reverb, delay...)
Nothing (nullroute, bitbucket, discard...)

jms

Neil J. McRae wrote:

I remember in the past an excellent system using Sesame Street characters names.

/me awaits super-super-grover...

http://www.faqs.org/rfcs/rfc2100.html

This only works in small shops. If you have more routers than muppets, you
have a problem. Had a lab once where we named machines after colors. That
hit some snarls when we discovered nobody in the lab could consistently spell
'fuschia', 'mauve', or 'paisley'. :slight_smile:

Star Trek Federation Starships... they seem to invent more daily, so no problems running out.

If your DNS is RFC3490-enabled, you can go for the Klingon and Romulan
ships too. Particularly handy if you're into security through obscurity. :slight_smile:

Doesn't scale though :frowning:

Hence the rapid emergence of southpark-naming-draft-001.txt,
flintstones-naming-draft-001.txt. Not to mention the grover /
super-grover / new-grover / new-super-grover incident.

Regards,
Tim.