>> I find it interesting that nobody so far mentioned RFC1178 (Choosing a >> name for your computer): ftp://ftp.rfc-editor.org/in-notes/rfc1178.txt. >> There are several excellent ideas in that document.
> Wow! Thanks. Been looking for that. That is a good reference, I agree. I could add one suggestion for the "names that work well" section. One model a colleague implemented is to choose a DNS name prefix then put the last two octets of the IP dotted decimal address as the suffix. For example, a prefix could be "PBC" then let's say we have two class C subnets, 15 and 16 off a subnetted 10.1.0.0 network. The DNS names would be PBC151 to PBC15254 for the 254 hosts on the 10.1.15 subnet and PBC161 to PBC16254 for the 10.1.16 subnet. With this simple formula you can get the IP address from the DNS name and vice versa (assuming you remember the first two octets). Systems come and go but the relationship between the DNS name and IP address does not. I find DNS "vanity names" often become obsolete after some time, be it weeks, months or years. > You will find that having VMIDs not matching hostnames > is just a pain. Rick, you're making me think. I've been using mundane VM user ID names like LINUX01. If the prefix above were limited to 2 characters, the DNS name would be limited to 8, thus being suitable for a VM user ID name. Then you could know any one of the IP address, DNS name or user ID, and be able to obtain the other two (!!:) "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
