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.

Consider a "Production" URL for a corporate web site called "Access"

access.company.com

I'm trying to weigh the pros and cons of different ways of defining a non-production site like "DEV":

(a) accessdev.company.com

(b) dev.access.company.com

(c) access.dev.company.com

(d) access.company.com.dev

We have traditionally gone with (a) but I've never been a fan of it. I like (b) because it is obvious that it is "dev". I like (c) because it makes a nice sub-domain standard that we could use for other "dev" servers. I find (d) interesting too, but it is a little odd not seeing .com at the end.

Is there a "best" answer here or is it more a "it depends" type of thing?

share|improve this question
2  
I can't see there being a best answer to this, it all depends how you want to work. I'm guessing that the server shouldn't be externally resolveable let alone accessible so either (c) or (d) would allow you to not serve the dev zone externally (c) or be totally unresolveable from the outside world (d). –  Dave Mar 15 '13 at 14:31
    
I agree with Dave, this is completely subjective. "What kind of sandwich should I have for lunch?". Pick what suits you. –  joeqwerty Mar 15 '13 at 14:40

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.