CNAME record not getting updated for a subdomain

Website, Application, Performance Getting Started
1

My domain is takemytickets.co.in, where I tried to create a subdomain for this domain and the subdomain should point to a server in aws ec2. So, I used CNAME record for this. Below is the configuration.

image
image1425×500 25.3 KB

But when I try to reach the endpoint, I’m getting site can’t reached error.
Kindly help me with this…

4

There’s no indication the CNAME hasn’t been updated. It’s a proxied record and resolves in DNS.

dig api.takemytickets.co.in

; <<>> DiG 9.10.6 <<>> api.takemytickets.co.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21222
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.takemytickets.co.in.	IN	A

;; ANSWER SECTION:
api.takemytickets.co.in. 300	IN	A	104.21.42.94
api.takemytickets.co.in. 300	IN	A	172.67.160.120

Cloudflare is returning a 521 error. You can review the troubleshooting steps for that particular error to resolve the origin issue.

1 Like
5

Hello,

521 error referring to webserver down.
You may want to check if the origin servers block Cloudflare IPs or Port 443 and Port 80.
Cloudflare IP range

I would strongly suggest you to check with the origin server provider.

I’ve run test to the CNAME target IP, and it’s showing port 443 (tcp) failed: Connection refused and Failed to connect to x.x.x.x port 443 after 220 ms: Couldn't connect to server.

Both Port 443 and Port 80 showing connection refused.

Redacting the IP for security purpose.

6

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.