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?
Asked
Active
Viewed 4,414 times
3
Kenny Rasschaert
- 9,045
- 3
- 42
- 58
Mike C.
- 151
- 1
- 4
-
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
-
I'm sure that this question has many duplicates, but the one linked to is NOT a duplicate of this actual question. – andrew lorien May 15 '18 at 04:16
2 Answers
2
It is always best to wait for a while when changing DNS configuration. It started working after a couple of hours.
Mike C.
- 151
- 1
- 4
0
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.
ceejayoz
- 32,910
- 7
- 82
- 106
-
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, 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