nanog mailing list archives
Re: Thoughts on best practice for naming router infrastructure in DNS
From: Cat Okita <cat () reptiles org>
Date: Fri, 29 Jun 2007 15:27:24 -0400 (EDT)
On Fri, 29 Jun 2007, Chris L. Morrow wrote:
perhaps a decent other question is: Do I want to let the whole world know that router X with interfaces of type Y/Z/Q is located in 1-wilshire. I suppose on the one hand it's helpful to know that Network-A has a device with the right sorts of interfaces/capacity in a location I care about, but it's also nice to know that for other reasons :( so naming things about mythic beasts or cheese or movies is not so bad, provided your NOC/OPS folks have a key that shows: optimus-prime.my.network.net == 1-wilshire, m160, t1-customers-only.
At 3am, I'd rather have the NOC/OPS folk be able to figure things out from the name directly, than have to have access to the magic key that lets them know what the weird name translates into. Ditto if I'm nowhere near my translation key, having a life, for example. At any rate - it's possible to have informative names without going into "too much" detail - knowing where the device is, what it does (border, core, switch), and what it's connecting (customerA) is pretty darn'd useful all around, and avoids getting into the device type and interface specifics. cheers! ========================================================================== "A cat spends her life conflicted between a deep, passionate and profound desire for fish and an equally deep, passionate and profound desire to avoid getting wet. This is the defining metaphor of my life right now."
Current thread:
- Thoughts on best practice for naming router infrastructure in DNS Olsen, Jason (Jun 14)
- Re: Thoughts on best practice for naming router infrastructure in DNS randal k (Jun 14)
- Re: Thoughts on best practice for naming router infrastructure in DNS Mark Tinka (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Leigh Porter (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Alexander Harrowell (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Chris L. Morrow (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Cat Okita (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Chris L. Morrow (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Leigh Porter (Jun 29)
- <Possible follow-ups>
- RE: Thoughts on best practice for naming router infrastructure in DNS Neil J. McRae (Jun 29)
- RE: Thoughts on best practice for naming router infrastructure in DNS Justin M. Streiner (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS David Freedman (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Pete Ehlke (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Valdis . Kletnieks (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Jeff Shultz (Jun 29)
- Re: Thoughts on best practice for naming router infrastructure in DNS Valdis . Kletnieks (Jun 29)