ha0124 Posted September 6, 2021 Posted September 6, 2021 You could always put two entries in the DNS. One as a useful name to identify what it is and a second more abstract name?
Garacesh Posted September 7, 2021 Posted September 7, 2021 In a small home lab, I'd probably end up giving my servers names from The Matrix, it seems rather fitting. Neo would be the DC, as he's the most important, The filer server would probably be called Tank, Dozer or Link as they're the ones uploading data.. In a big domain though? Functional names. DC01, File-Server, HyperV-01, Print-Server, MECM, etc
Jcx500 Posted September 7, 2021 Posted September 7, 2021 In Homelabs and work I’ve always kept it simple DC01 File01 Hyperv01 WDS01 Apps01 Adfsproxy01 Adfs01 You get the idea [emoji16]
round2it Posted September 8, 2021 Posted September 8, 2021 hyper v hosts - kingdom then just dc-01 dc-02 etc
TechMonkey Posted September 8, 2021 Posted September 8, 2021 Location-Virtual/Physical-Purpose. So MB1-V-DC01 for Main building, virtual DC 1. Cattle not pets. How do you automate including or excluding servers if they have random hilarious names? The only way is to either keep a database of what purpose each name does or manually include each name in each script. No one got time for that.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now