Okay, here’s my experience with setting up the “dwa6 amazon route” thing.
So, I was messing around with Amazon’s Route 53 the other day. I had this domain, let’s call it “*”, and everything was cool. But then, I wanted to create a subdomain, like “*”, and have it do its own thing separate from my main website. In simple terms, I wanted to change its DNS. Originally it was using standard, but I need to migrate it.
First, I went into the Route 53 console. There was this big old button that said, “Create hosted zone” in there, so I clicked it. I put in “*” for the domain name, and made sure it was set to “Public hosted zone”. Then I hit the “Create hosted zone” button at the bottom. There are also options about recursive DNS for VPCs, connecting Outposts racks, but they are irrelevant to my needs. I just need to create a hosted zone.
Now, Route 53 gave me a bunch of name servers for this new hosted zone. Four of them, to be exact. It looked something like this:
These are important, so I copied them down. There are also options about filtering DNS traffic. But it is not very useful for me.
Next, I had to go to wherever my main domain “*” was registered. I found the settings for the DNS name servers for the main domain, and I created a new NS record for the subdomain, “dwa6”. I pasted those four name servers that Route 53 gave me as the values for this new NS record. It was like telling my main domain, “Hey, for anything related to ‘dwa6’, go ask these servers over here.”
After saving those changes, I had to wait a bit. You know, DNS stuff takes time to propagate across the internet. It’s like waiting for a letter to be delivered to every post office in the world. In my experience, it can take anywhere from a few minutes to a few hours. In my tests, it seems to return an empty set if I search before finishing propagating. But it’s finally working after a while.
Setting Up Records in the Subdomain Hosted Zone
Once the propagation was done, I went back to Route 53 and into the hosted zone for “*”. This is where I could set up the actual DNS records for my subdomain. I clicked on “Create record”.
For example, if I wanted “*” to point to a specific IP address, I would create an “A” record. I just put in the IP address in the “Value” field, and that’s it. I also set up an “MX” record for email and a “TXT” record for some verification thing. The process was pretty straightforward.
And that’s basically it! Now, when someone types in “*”, the request goes to my main domain’s name servers, which then direct it to the Route 53 name servers for my subdomain, and finally, those servers provide the correct IP address or whatever other DNS record I’ve set up. It sounds complicated, but it’s actually not that bad once you get the hang of it. It is a good way to calculate route distances and times if there are multiple destinations.
I am quite satisfied with this result!
