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 interfac
On Fri Jun 29, 2007 at 16:35:09 +0100, Neil J. McRae wrote:
>
>I remember in the past an excellent system using Sesame Street characters
>names.
http://www.faqs.org/rfcs/rfc2100.html
Neil J. McRae wrote:
I remember in the past an excellent system using Sesame Street characters names.
/me awaits super-super-grover...
On Fri, 29 Jun 2007, Neil J. McRae wrote:
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.
Workstation
On 6/14/07, Olsen, Jason <[EMAIL PROTECTED]> wrote:
Neither one of these seems well-equipped to deal with "virtual"
interfaces such as an ethernet interface that is VRRP or HSRP'd between
two routers (eg x.x.x.10 is your "virtual" IP for the subnet's gateway,
router 1 has physical interface IP
I've found myself with a few spare cycles and have decided to put them
towards addressing a pet peeve I frequently encounter here: the complete
state of chaois that is the naming in DNS for our network
infrastructure. There are mismatched forward and reverse entries, no
designated subdomain for W
