- Newest
- Most votes
- Most comments
Right, positive things appear to be happening Two notifications have appeared:
androit-solutions.com Name server update successful 2023-01-01 22:41:51 androit-solutions.com Domain registration successful 2022-12-26 14:03:45
dns lookup is also looking good
I will give this some time to propagate but I would still appreciate it if you could check over the other infos that I have inputted. I came within the width of a ballhair away from ditching AWS, I suspect its something to do with the website GUI and it was incredibly annoying
When you register a domain with Route 53, it automatically creates a hosted zone for that domain. But it seems that no hosted zone is currently associated with your domain androit-solutions.com as it is not possible to find any name server for this domain. Hence, if you created the public hosted zone that you are currently using separately, please consider updating the name servers in the below record for your domain.
androit-solutions.com NS Simple - ns-1581.awsdns-05.co.uk ns-115.awsdns-14.com ns-755.awsdns-30.net ns-1266.awsdns-30.org
Instruction on how to update the name servers for a registered domain is provided in the link below:
Adding or changing name servers or glue records
More details on replacing a hosted zone for a registered domain can be found here:
Replacing the hosted zone for a domain that is registered with Route 53
Hope this helps!
I think I might be getting somewhere here...for some unknown and go awful reason I have only now received an Email saying that my name servers have been updated
I have been updating from the GUI in pic2 and I never ever got an Email confirming the update until I tried the GUI in pic 1
I was told to update SOA records by support, they gave me:
ns-1581.awsdns-05.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
I don't know if thats right im a bit suspicious
Please let that be it that was so frustrating
I think you might be better served by using a CNAME to point to the cloudfront distribution.
Details below . . .
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html
Also check If your domain's NS records properly updated in Route53? https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html
Is your S3 bucket setup to host static websites? https://docs.aws.amazon.com/AmazonS3/latest/userguide/HostingWebsiteOnS3Setup.html
Thanks but i've been through the literature many times and its not up to date, many of the links it refers to are simply not there, something that support doesn't seem to understand. There are no DNS records for the domain they simply won't update. I have already tried the CNAME. S3 buckets are configured and working as is cloudfront.
Relevant content
- asked 2 years ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Glad to hear that it started to work. NS records are looking good and the domain is now resolving. Are you facing any other issue that you need help with?
Yeah everything is fine apart from the site not being secure if I use the domain. CloudFront distribution is still safe and SSL cert still valid - what on earth went wrong with that?
You site is now loading on both http://androit-solutions.com and https://androit-solutions.com. In order to enforce the site to only load on https, you need to update the setting in your Viewer Protocol Policy under Behaviors as explained in the link below:
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-https-viewers-to-cloudfront.html