Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I'm trying to get my development environment as such:

dev.domain.com
dev.admin.domain.com

qa.domain.com
qa.admin.domain.com

I've created them just like I would create a sub-domain on the Route 53 page but it does not work. Anything I am missing?

share|improve this question

marked as duplicate by Michael Hampton, ceejayoz, pauska, mdpc, dunxd Mar 26 '13 at 11:30

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

    
This has nothing to do with S3... – ceejayoz Mar 25 '13 at 17:27
    
I thought specifying my environment might be of importance. – Mike C. Mar 25 '13 at 18:48
    
You're creating a subdomain in Route53, not S3. S3's a file storage system. – ceejayoz Mar 25 '13 at 18:53
    
Ok, changed the title! – Mike C. Mar 25 '13 at 19:12

It is always best to wait for a while when changing DNS configuration. It started working after a couple of hours.

share|improve this answer

You can't do something.*.example.com.

You can do *.example.com, which'll cover all of them, or change the order to something sensible like admin.dev.domain.com, *.dev.domain.com, admin.qa.domain.com, *.qa.domain.com, etc.

share|improve this answer
    
qa.*.domain.com was meant as qa.whatever.domain.com. I created a qa.admin.domain.com and I will not ping. – Mike C. Mar 25 '13 at 18:44
    
Again, you can't do something.*.domain.com. It won't work. – ceejayoz Mar 25 '13 at 18:47
    
Again, I don't want to create something.*.domain.com. I want to create many sub domains and have qa, dev and staging subs for all of them. – Mike C. Mar 25 '13 at 19:17
    
So just do *.domain.com and have the server handle the rest. You can't do what you're trying to do solely with DNS. – ceejayoz Mar 25 '13 at 19:27
    
It works now, I guess it just required propagation, funny that the sub domain worked instantly. I think the * is confusing you in my question. I will change the question. – Mike C. Mar 25 '13 at 19:31

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