Slashdot Mirror
Why Do We Name Servers the Way We Do?
jfruhlinger writes "If you use a Unix machine, it probably has a funny name. And if you work in an environment where there are multiple Unix machines, they probably have funny names that are variations on a theme. No, you're not the only one! This article explores the phenomenon, showing that even the CIA uses a whimsical server naming scheme." What are some of your best (worst?) naming schemes?
There's a pretty sizeable collection of funny/clever server names on Stack Overflow here:
http://stackoverflow.com/questions/262657/the-coolest-server-names
Sturgeon was an optimist.
Actually, the "piles of medical evidince" have lead the American Association of Pediatrics and the American Medical Association not to recommend routine circumcision of newborns. Given the number and density of nerve endings in the foreskin, comparison to clitoridectomy is not so far-fetched. Just because the one is socially accepted where you live doesn't make it any less barbaric than the other.
I personally hate that naming scheme, it's confusing and produces long, hard to remember and typo-prone hostnames.
NS records exist for a reason. Your example could just as easily be:
windb002.syd
Since every Windows network (and that tends to be where I see domain names like that) is a real DNS domain, there's no reason you couldn't do this. This has the added benefit of being able to push a DNS search domain based on the location of the computer doing the DHCP request, then having certain hosts that are replicated in each area subdomain, for example a CMS or a DB. Does sydwindb002 replicate to nycwindb002? Have windb002.syd replicate to windb002.nyc (and vice versa) then let users just put in windb002, and traveling users will be able to automagically use the closest and probably fastest DB server.
Or, in the case of a CMS, have one top-level CMS that refers to local ones. Say you have cms.example.com and cms.xxx.example.com. Depending on your network location, typing in CMS will either take you to the top-level CMS or the local one, which might aggregate data from the top-level one.
There's an old saying that says pretty much whatever you want it to.
I thought this was a good idea until the first time we moved an office...