Score:0

Server

How to redirect an old subdomain with Route53

Costa Michailidis

6/21/23, 3:52 PM

I've redirected an old subdomain blog.mysite.com to my homepage mysite.com with a CNAME record in Route53, but.... it doesn't work. I get no server response at all.

Is there something I'm doing wrong?

Update: Now I get a 403 from Cloudfront.

0 + 0

cname-record

amazon-web-services

amazon-route53

Tim

6/22/23, 12:42 AM

It's difficult to help when you redact the key information required for problem solving. Also note that sending a request to a different server doesn't mean that server will accept the request or send back useful content, you may need to have it listen for requests to the old domain and redirect / forward the request.

Costa Michailidis

6/22/23, 2:18 PM

Sorry, I've been punished for using real URL's back at Stackoverflow. I see, so the receiving server is thinking it needs to serve up for the original URL? Is there a way to redirect at the DNS level? A DNS record that says, 'hey the blog subdomain just reroutes to the www subdomain.' Meaning, can I rewrite the request with DNS before passing it?

Tim

6/22/23, 5:02 PM

A receiving server can effectively have a wildcard accept, accepting and servicing any request that comes in, but that's not the default. If the request is http it's fairly easy to do a wildcard redirect in Nginx / Apache, but if it's https the connection needs to be terminated. My suggestion is to configure your web server to accept that domain, which may include presenting the correct https certificate for the old domain, then having the web server send a permanent redirect - test it with a temporary redirect first. This may or may not be your core problem, but it will be a problem.

Costa Michailidis

6/22/23, 9:49 PM

Alright! All working now. It involved using S3 for a redirect, putting Cloudfront in front of that, and routing an A record to the Cloudfront site.

Tim

6/22/23, 9:51 PM

I'll provide an answer so you can mark it done. Feel free to provide your own detailed answer instead.

Score:1

Server

Tim

6/22/23, 9:52 PM

I suspect the problem is you are routing a request to a server that is not configured to accept requests for that domain.

My suggestion is to configure your web server to accept that domain, which may include presenting the correct https certificate for the old domain, then having the web server send a permanent redirect - test it with a temporary redirect first. There are multiple other ways to do this, including the S3 static website option you mentioned in the comment above.

0 + 0

Costa Michailidis

6/24/23, 12:11 AM

Thanks! That's the approach I ended up taking. If anyone has this issue and needs to details, let me know. It's like 19 steps on AWS, as with all things AWS : )

Tim

6/24/23, 3:04 AM

You could add your own answer to give details, and change the correct answer from yours to mine, if you like.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: How to redirect an old subdomain with Route53

TH: วิธีเปลี่ยนเส้นทางโดเมนย่อยเก่าด้วย Route53

RO: Cum să redirecționați un subdomeniu vechi cu Route53

RU: Как перенаправить старый субдомен с помощью Route53

VI: Cách chuyển hướng tên miền phụ cũ bằng Route53

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.