Skip to content

CNAME issues only for one domain/account

0

Hi,

I have a domain registered through Route 53 and have been trying to add a CNAME. No CNAME I use seems to work for this domain, but I have another account with a different domain and that works fine. I have reproduced the exact same thing in both, but yet see completely different results.

The test record: foo.mannanlive.com. CNAME www.google.com.
I have waited 72 hours and it doesn't work. On the account where it does work, it is instant.

This is the one that doesn't work:

dig foo.mannanlive.com _nostats _nocomments +nocmd
;foo.mannanlive.com. IN A
mannanlive.com. 658 IN SOA ns-1237.awsdns-26.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

This is the one that does work:

dig foo2.rosterportal.com _nostats _nocomments +nocmd
;foo2.rosterportal.com. IN A
foo2.rosterportal.com. 7 IN CNAME www.google.com.
www.google.com. 253 IN A 172.217.25.164

Interestingly foo.rosterportal.com did work, but after deleting it and re-adding it, it no longer works.

dig foo.rosterportal.com _nostats _nocomments +nocmd
;foo.rosterportal.com. IN A
rosterportal.com. 349 IN SOA ns-1637.awsdns-12.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

asked 5 years ago290 views
1 Answer
0

Ok figured it out, if anyone runs into this issue: the mannanlive.com was registered in Amazon Lightsail -> Networking -> DNS Zones.
So any changes to the Route 53 entries seem to be completely ignored, there are no warnings or anything that what you are doing is not ever going to work.

Hope that helps someone.

answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.