Having thousands of servers it's typically best to name them by their location itself.
Example H-17 RU4 etc
Being row H, rack 17 RU4.
Another if you need to know location as well NYC-H17-RU4 SEA-4.42-RU4 etc.
This is quite helpful to know and speed things up. We personally like doing this and it's how systems are most times deployed at least on our end as clients often change the hostname once they get it. However, it keeps things stupid simple for techs to know which server it is for doing any tasks on.
Paid servers with dedicated IPv4 are named vps0 ~ vps9.
Free servers and IPv6-only/NAT servers are named box0 ~ box9.
I only allow myself 10 servers in each category.
VPS bundles are named after their provider followed by airport code.
For example, WebHorizon NAT bundle Poland location has the name whz-waw.
In fact, hostname in Virtualizor is waw, but my SSH config refers to it as whz-waw.
Laptops and phones are named sunny followed by a letter or digit that indicates its brand or model.
For example, my Windows 7 laptop was named sunny7.
The dedicated server in my closest is simply named d, as it's DELL brand.
Containers on this machine are named like d-video, where the suffix indicates purpose.
Servers I manage in my workplace lab are named as relevant project followed by a digit, such as iot2.
We accept Karma donations for the last flan. 🍮 affbrr
I don't have one consistent method. One of my work sites is Hitchhikers Guide, Virmach servers are predominantly Greek ( gods,titans, heros ), Hosthatch is a mix of TMNT and Marvel, Web Horizon are famous lighthouses....
Fighter aircraft: High performance nodes, focused on computational power.
Cargo/commercial aircraft: Nodes focused on data storage.
Miscellaneous aircraft: Other very low-end nodes. (Think low end NAT hosts, that sort of thing)
Cheap dedis are my drug, and I'm too far gone to turn back.
I like to use [prefix]-[IATA code]-[two digit number] to name my servers. So, a production server for example.com in Dallas, TX might get the name excom-prod-dfw-01, and a server used as development workspace in Amsterdam, NL might get the name dev-wsp-ams-01, and so on.
Pretty boring at the moment - Just based on the location of the server (most are VPSes).
It's starting to annoy me a bit though, since I was inconsistent with when I used country ISO code (e.g. ch** for Switzerland, ca** for Canada) vs when I used region or city (e.g. la** for Los Angeles, syd** for Sydney). I think my idea was just to use city/region in areas where I have many servers and country in areas I only have one server, but I haven't done it consistently.
When I was in university, some friends and I shared a dedicated server. The server was called "Springfield" and all the Linux-VServer containers on it were named after Simpsons characters.
My personal servers are named by country, like us1, us2, jp1, nl1, nl2, uk1 etc.
But I rarely use those names anywhere but in monitoring, since all the services are pointing to dns aliases.
Easy to remember and easy to spell. If it were not for the later I'd do nordic gods, but Höðr in a console may take a while if I'm using a UK keyboard on a US server...
All my servers are named after starship names from star trek, star wars, stargate, etc.. or they are named after sexy women. Prod servers are named after purpose and location.
Vladimir S. - IT Consultant, Entrepreneur, Web Developer, and Disability Advocate.
I thought this was a super clever thing to do until I got in trouble for it. Now I use superhero's real names (like Beast, real name Hank McCoy, vps name "hank").
I ain’t reading all that, but I’m happy for you though. Or sorry that happened.
I've tried many naming schemes, I'm consistent only on this one:
"ISO country code"-"name of a random Roman/Greek/Viking deity"-" generic purpose"
example: DE-thor-mail, SG-vulcan-proxy, FR-minerva-server
alias & RDNS:
"purpose"."digits"."domain"
example: mail$(two_digits_number).$(real_domain_name), proxy$(two_digits_number).$(real_domain_name), server$(two_digits_number).$(real_domain_name)
root is always disabled and the sudoer is always named after an emperor. Ex. nero@mail02....
The combination emperor+deity reminds me of each server job more than anything else. Even if it's completely unrelated to anything tech related. An additional tmux script reminds me what the hell is Nero doing with Thor in Germany. He's doing Mails! It's obvious, isn't it?
Comments
rock should be a guest too, and rename the host. Otherwise scissors can never win.
Karen01
Karen02
...
I bench YABS 24/7/365 unless it's a leap year.
I name them after waterbodies or mountains near the location.
So a server at Serverius in Dronten could be ‘Veluwemeer’ and my VM in Sofia is called ‘Vitosha’.
Having thousands of servers it's typically best to name them by their location itself.
Example H-17 RU4 etc
Being row H, rack 17 RU4.
Another if you need to know location as well NYC-H17-RU4 SEA-4.42-RU4 etc.
This is quite helpful to know and speed things up. We personally like doing this and it's how systems are most times deployed at least on our end as clients often change the hostname once they get it. However, it keeps things stupid simple for techs to know which server it is for doing any tasks on.
PureVoltage - Custom Dedicated Servers Dual E5-2680v3 64gb ram 1TB nvme 100TB/10g $145
New York Colocation - Amazing pricing 1U-48U+
https://namingschemes.com/Main_Page
If ever anyone needs ideas.
"The imitator dooms himself to hopeless mediocrity." — Ralph Waldo Emerson
For my private servers I use periodic elements. For me it is quite easy to remember.
Paid servers with dedicated IPv4 are named vps0 ~ vps9.
Free servers and IPv6-only/NAT servers are named box0 ~ box9.
I only allow myself 10 servers in each category.
VPS bundles are named after their provider followed by airport code.
For example, WebHorizon NAT bundle Poland location has the name whz-waw.
In fact, hostname in Virtualizor is waw, but my SSH config refers to it as whz-waw.
Laptops and phones are named sunny followed by a letter or digit that indicates its brand or model.
For example, my Windows 7 laptop was named sunny7.
The dedicated server in my closest is simply named d, as it's DELL brand.
Containers on this machine are named like d-video, where the suffix indicates purpose.
Servers I manage in my workplace lab are named as relevant project followed by a digit, such as iot2.
We accept Karma donations for the last flan. 🍮 affbrr
I don't have one consistent method. One of my work sites is Hitchhikers Guide, Virmach servers are predominantly Greek ( gods,titans, heros ), Hosthatch is a mix of TMNT and Marvel, Web Horizon are famous lighthouses....
I used to try to give interesting, unique names, but found it's easier to just be generic with it.
NL-00, NL-01, NL-02, etc, etc.
[ IncogNET LLC ] - Since 2020
[ The Internet Speech & Privacy Company ]
Named after ex girlfriend’s
blog archives
is that why 2 are down now?
I bench YABS 24/7/365 unless it's a leap year.
Covid got them.
blog archives
https://en.wikipedia.org/wiki/NATO_reporting_name#Aircraft
Fighter aircraft: High performance nodes, focused on computational power.
Cargo/commercial aircraft: Nodes focused on data storage.
Miscellaneous aircraft: Other very low-end nodes. (Think low end NAT hosts, that sort of thing)
Cheap dedis are my drug, and I'm too far gone to turn back.
Obligatory xkcd https://xkcd.com/910/
I like to use
[prefix]-[IATA code]-[two digit number]to name my servers. So, a production server for example.com in Dallas, TX might get the nameexcom-prod-dfw-01, and a server used as development workspace in Amsterdam, NL might get the namedev-wsp-ams-01, and so on.some random animal names
toogoodtopassup
herewegoagain
walletbreaker
thistimeyoureallyfuckedup
youdontevenneedme
stopbuyingalready
gogethelp
definitelythelastone
itsonlyonedolla
oohexoticlocation
whyareyoulikethis
mightdeadpoolbutcheeeap
fomo11
definitelyneededperu
apacforabetterprice
willusethisonelaterthisyear
dontforgettocanceltheotherone
wellfucknowihavethreeofthese
damnyouvirbot
damnyouvirbot2
damnyouvirbot3
abittoofarbutareallygoodprice
iwishihadthisineurope
damnyouvirbot4
damnyouvirbot5
aussieaussieaussieoioioi
Food for thought:
Next time I will name the servers based on the coupon code (or the name of the plan offered).
blog archives
I do proper names of stars, for now no duplicate starting letters but I'll loop back around at some point.
Chicago1
Seattle1
I name them by role.
wg = WireGuard
etc
etc
♻ Amitz day is October 21.
♻ Join Nigh sect by adopting my avatar. Let us spread the joys of the end.
But how does the sequence end?
Since the end is nigh, it's just those three.
"The imitator dooms himself to hopeless mediocrity." — Ralph Waldo Emerson
Rinse and repeat?
Nigh1
Nigh2…
etc
blog archives
4 is death.
♻ Amitz day is October 21.
♻ Join Nigh sect by adopting my avatar. Let us spread the joys of the end.
Pretty boring at the moment - Just based on the location of the server (most are VPSes).
It's starting to annoy me a bit though, since I was inconsistent with when I used country ISO code (e.g.
ch**for Switzerland,ca**for Canada) vs when I used region or city (e.g.la**for Los Angeles,syd**for Sydney). I think my idea was just to use city/region in areas where I have many servers and country in areas I only have one server, but I haven't done it consistently.When I was in university, some friends and I shared a dedicated server. The server was called "Springfield" and all the Linux-VServer containers on it were named after Simpsons characters.
Daniel15 | https://d.sb/. List of all my VPSes: https://d.sb/servers
dnstools.ws - DNS lookups, pings, and traceroutes from 30 locations worldwide.
I use a dull name scheme for my server
FORMAT: function-NUMBER.COUNTRY-CODE.DOMAIN, for example
My scuffed GlusterFS cluster™ made up of KS-1s is collectively called
yo-mommaSurely you don't have a FAT filesystem on top of that?
Unfortunately I don't, would've been funnier if the underlying drives were. Maybe next time.
My personal servers are named by country, like us1, us2, jp1, nl1, nl2, uk1 etc.
But I rarely use those names anywhere but in monitoring, since all the services are pointing to dns aliases.
The lamest scheme of them all - ancient gods
Easy to remember and easy to spell. If it were not for the later I'd do nordic gods, but Höðr in a console may take a while if I'm using a UK keyboard on a US server...
my pass at line 17 btw
dave01
dave02
dave03
dave04
dave05
dave06
dave08
dave09
dave10
And so on, so forth
dave-f+ed
sounds great too
You need at least one called chas.
Why are you registered here then when you have zero servers at all?
All my servers are named after starship names from star trek, star wars, stargate, etc.. or they are named after sexy women. Prod servers are named after purpose and location.
Vladimir S. - IT Consultant, Entrepreneur, Web Developer, and Disability Advocate.
[email protected] | www.ivlad.net
What makes you believe I have zero servers? ^.^
blog archives
I couldnt resist making that joke
Took from navy ships of different countries. If there are multiple locations within that country, name after the city/provider.
As I own 100+ servers I follow this naming method.
1st Alphabet denotes its purpose - W
2nd Number of Servers used for that purpose - 01
3rd City - Houston
4th State - Texas
5th Provider - DataIdeas
So it will be W-01-Houston-Texas-DataIdeas
As soon as my monitor notified me about the downtime, I got all the info needed.
IP:
xxx.xxx.123.4
LA234
xxx.xxx.123.45
SYD345
xxx.xxx.123.456
SG456
Location: LA, SYD, SG
I thought this was a super clever thing to do until I got in trouble for it. Now I use superhero's real names (like Beast, real name Hank McCoy, vps name "hank").
I ain’t reading all that, but I’m happy for you though. Or sorry that happened.
Lol
Was this before Cloudflare era?
Now I can show the Mrs:
"Look, even Cloudflare uses names like
pat.ns.cloudflare.com
tony.ns.cloudflare.com
so also
Bob
Stan
Lola
Amir ..."
I am just naming the servers after women instead. "
Working well so far.
Edit:
Turns out some one compiled a list of all 900 of CF nameservers
https://github.com/indianajson/cloudflare-nameservers
blog archives
I've tried many naming schemes, I'm consistent only on this one:
"ISO country code"-"name of a random Roman/Greek/Viking deity"-" generic purpose"
example: DE-thor-mail, SG-vulcan-proxy, FR-minerva-server
alias & RDNS:
"purpose"."digits"."domain"
example: mail$(two_digits_number).$(real_domain_name), proxy$(two_digits_number).$(real_domain_name), server$(two_digits_number).$(real_domain_name)
root is always disabled and the sudoer is always named after an emperor. Ex. nero@mail02....
The combination emperor+deity reminds me of each server job more than anything else. Even if it's completely unrelated to anything tech related. An additional tmux script reminds me what the hell is Nero doing with Thor in Germany. He's doing Mails! It's obvious, isn't it?
I need holidays
They are all named earth. 🌍
Cause they works on earth. 😂
HostCram LLC - Web Hosting Built For Speed, Reliability, Security & Uptime! [We operate AS39618]