3 ms·
<function>-<environment>-XYnn.<DC Airport Code><Number>.company.com foo-prod-1101.sea1.company.com foo-dev-1201.sea2.company.com foo-test-2101.ord1.company.com
by lamontcg 13y ago
<function>-<environment>-XYnn.<DC Airport Code><Number>.company.com
foo-prod-1101.sea1.company.com
foo-dev-1201.sea2.company.com
foo-test-2101.ord1.company.com
'foo' is whatever, and 'mysql' is bad while 'corp-db' is better as other commentators mentioned.
for XYnn match X to the airport code of the datacenter, match Y to the sequence number of the datacenter, and 'nn' is a 2-digit code for the number in the cluster.
all short names are unique this way. all datacenter can have a mix of prod/int/dev/test. you can use DNS name resolution search path to lookup services like 'ldap' in your local datacenter.
don't use serial numbers. foo-123456789 is annoying for humans to use and will get truncated with interesting results. i had a discussion one time on chat with another engineer where i was looking at box '123' and he was looking at box '789' and we were both getting real confused because it seemed like we were on the same box... because we were...
also only use "company.com" as your domain for every server and desktop in your company. if you need "company.co.uk" then it should only host websites "www.company.co.uk" that points at VIPs and the servers behind that should all still live in company.com. if you have windows boxes then setup a domain for AD "ad.company.com" or "win.company.com" and let your domain servers own that and setup proper DNS delegation from the parent.