Server Naming Conventions?
The reader continues:
"Here's a few ideas we've been tossing around, using Joe's Deli as an example:
- [four letter "name"][two letter service type][2 numbers]
eg) jdelwb03.domain.com
+ easy to determine the function and name
- hard to remember and pronounce, once you run out of four
character servers, determining the name and function will be
difficult. Joe's Deli and John's Delivery will have conflicting
names
- [random combination of numbers and letters]
eg) ak1jop3d.domain.com
+ none really
- confusing.. really confusing. Can you imagine saying to someone
"log on to alpha kappa one john omikron peter three delta?"
- [theme based name]
name servers based on a theme, eg Gundam
eg) zaku.domain.com, gelgoog.domain.com
+ easily identifiable - all Gundam names belong to Joe's Deli,
easy to pronounce and remember
- hard for a new tech or management (why would they need to know?)
to associate to a server
"I'd like to know what others in the tech community use for server naming policies when planning large scale data centres. Also, with data centres located nationally, does the naming convention pose any problems? Thanks."
1st_post
2nd_post
3999th_post
Fear: When you see B8 00 4C CD 21 and know what it means
mov ax, 4c00h
int 21h
Result: terminate program under DOS, exit code 0.
Alex
Fear my assembly skills.