> I think that cutesy names like this are fine for personal use, but for commercial use you're better of using a more standardised schema for naming. The thing

> I think that cutesy names like this are fine for personal use, but for commercial use you're better of using a more standardised schema for naming. The thing to keep in mind when doing this, too, is that DNS is a hierarchy. Use that. Many companies have a naming scheme something like EX-AP-NY-FS-1 for Example Corp's Appliance Division's New York Office's File Server number 1. Try fs1.ny.ap.example.com instead. It's much cleaner, and then the New York office can have ny.ap.example.com as a search domain and refer to it as just fs1 even if there is some other fs1 in the San Francisco office. People in SF can still access the New York server and vice versa by using the fully qualified name. It also puts administrative boundaries in the right place, so the appliance division has authority over its own names but not the names belonging to some other division.