Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm wondering if there are any widely used and proved naming conventions for DNS entries, for example let's say I've a company domain, like foobar.net and I've a bunch of services like a db for an application of our french branch, I'd though of db.myapp.fr.foobar.net.

I don't mind being verbose as I'm really not confident with abstract names like strasky.foobar.net and hutch.foobar.net to define my hostname.

Thanks

share|improve this question

closed as primarily opinion-based by ceejayoz, Greg Askew, Boris Guéry, Falcon Momot, kce Sep 4 '13 at 0:35

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
Strasky and Hutch? I wonder what kind of Russian POS car those guys drove. –  TheCleaner Sep 3 '13 at 19:16
    
Yes! whatever you like? –  Matt Sep 4 '13 at 0:45
    
This got addressed at some length in serverfault.com/questions/479945/… . –  MadHatter Sep 4 '13 at 5:59

3 Answers 3

Nope, it's totally a free-for-all. Whatever works for your company is what works for your company.

share|improve this answer
    
I bet, but there may be some proven solution or feedbacks from experienced people :) –  Boris Guéry Sep 3 '13 at 17:42
1  
These days so little is directly accessible from the public internet that most of my clients are hosting everything from www using content redirection within their load balancers to route stuff to different servers so that everything is masked to the user. –  mrdenny Sep 3 '13 at 17:53
    
I agree, but for example, I'm currently working with AWS, and their dns entries are not really straight-forward, let's say I've a managed Elastic Load Balancer, the dns is like 200 random chars, so even if it is not publicly accessible it may be through a bastion server, and using consistent naming seems a good practice to me, and when managing hundred of services I'd like to have fairly intention revealing name which helps remember them. –  Boris Guéry Sep 3 '13 at 17:59
    
There is no "proven solution" from "experienced people". Literally every client I have ever worked for has found some radically different and unique schema for this. Just make something up that will fit your business correctly. –  Falcon Momot Sep 3 '13 at 18:11

Much like naming your children or your pets, naming conventions are completely subjective. While there may be some tendency toward standardization within an organization, it's completely up to the organization or individual.

share|improve this answer

One piece of advice - which does not directly answer your question, admittedly -

DON'T USE HOSTNAMES FOR SERVICES. Because hostnames will change, eventually. Ideally, from the start, they will be abstracted behind some sort of scalability mechanism (DFS, load-balancing VIPs, HA cluster VIPs, etc). Don't depend on fred.example.org being the SMTP relay. Have a CNAME, smtp-outbound.example.org that points to fred, so that when you add wilma as a second (or replacement) relay server, you don't have to change the config files on all of your hosts that send mail.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.