can someone help me with this problem. I believe I am using the correct DNS record; ANAME(Alias record) for this but it is not working. I am using a third party domain name management instead of using the inhouse DNS 53 from AWS. I created a react application using amplify from aws but I am not able to point a record from my DNS. I have successfully added the DNS record(as you can see in the photo) but when I go to the record site it gives me the error below.
Thank you!!
enter image description here
enter image description here
You can follow some steps to achieve this :
Once you set up AWS Amplify
For Host, enter only the subdomain. For example, if your subdomain is www.example.com, enter www for Host.
For Points to, look at your DNS records in the Amplify Console and then enter the value. If the Amplify Console displays the domain for your app as xxxxxxxxxxxxxx.cloudfront.net, enter xxxxxxxxxxxxxx.cloudfront.net for Points to.
I think one correction you have to do is instead of amplify endpoint you have to get cloudfront endpoint as per step 3.
More details can find here : https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html
Related
I'm trying to host a custom domain name using Amplify & Namecheap. It hosts the website for a day or so, and then it says "the domain association has failed because we couldnt find the correct CNAME records."
This is currently what my amplify console looks like.
Amplify Console Message
This is what my namecheap DNS settings currently are.
This is what the DNS propagation comes up as
Help would be greatly appreciated!
As per title, for some reason I'm unable to connect the deployed app on Amplify to a custom domain provided on Route 53.
Here's the app deployed with Amplify: https://master.dwog1beoc1uv7.amplifyapp.com/
On Route 53, I created a hosted zone and added a CNAME record which should connect the custom domain to the domain where amplify hosts the app:
I then went to Amplify and added a new domain for the application:
If I now go back to Route 53, I can see the records have been automatically updated as followed:
Although everything seem setup properly, the custom domain (http://alessiopetrin.com/) doesn't work just yet.
If I test the record on Route 53, all seem fine:
I understand I should allow some time for the DNS propagation to take effect (up to 24h for what AWS states), but the time is almost up and I can't see it working, which make me think something is off.
As per second screenshot, I can see on Amplify that is waiting me to add the CNAME record in order to activate the domain, so I may think that could be the missing piece; Problem is the record has been assigned automatically already on Route 53, so not really sure if I should add the record somewhere else as well?
Apologise if I'm asking something obvious, and thank you in advance for the help!
The records added by Amplify are correct. I executed dig command on your domain and observed "SERVFAIL" status. This error is due to the mismatch in the name servers.
The following name servers are used currently.
ns1.dynadot.com
ns2.dynadot.com
Ref: https://www.whois.com/whois/alessiopetrin.com
Please set the name servers to the NS record of hosted zone (https://i.stack.imgur.com/U6Lj8.png). Refer below docs:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing
Then, delete the domain from amplify and try re-adding it. It should work.
Be careful that the require cname ask by aws to generate the SSL is mandatory and should has the following form :
An obvious error in Route53 is that Value/Route traffic goes to https://master.dwog1beoc1uv7.amplifyapp.com/. When you add CNAMEs, you don't add the protocol, but only the domain name. It should be master.dwog1beoc1uv7.amplifyapp.com
EDIT
There is a problem with the Cloudfront Distribution. I can't tell, if this is because something you did or it is an amplify problem. You need to somehow debug the distribution. Go to Cloudfront service in AWS console and locate your distribution. Some things to check:
Alternate domain is correct (your custom domain)
SSL certificate is correct
Go to behaviors tab and click edit:
An S3 bucket with your code should be used as an origin
There should be no caching on Headers
I am trying to use a custom domain name on AWS Amplify.
Step 2 in the process is:
2. Configure root domain In order to use your root domain you must configure an ANAME record (also called an ALIAS) in your DNS provider.
If your DNS provider does not support ANAME/ALIAS, migrate your zone
file to Amazon Route53. Learn more If you are migrating a custom
domain that is already serving production traffic, please wait until
your new application loads successfully at the .cloudfront.net url
shown below before updating your DNS records:
The values I need to plug in are:
#
ANAME
abc-whatever-xyz.cloudfront.net
Please note that Freenom does not have a type called "ANAME". However, there is "A" as well as "AAAA". If I use the "A", and plug in the values I receive the following warning:
Error occured: Wild cards are not allowed!
What should I do please?
To make your AWS Amplify app available under https://your-domain.org you need to create an A record, more specifically an ANAME / ALIAS record. You can transfer your host zone to AWS Route 53 as described here https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html if your DNS Service does not support ANAME / ALIAS records.
After you have switched your DNS Service to AWS Route 53 and the AWS name servers are in use you need to add the ANAME / ALIAS record. I found that the most straightforward way to do so is via the AWS Amplify console. Go to your app and then to Domain management. If you haven't already setup up a domain for your AWS Amplify app, follow the guide here https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html. Click on Manage Subdomains and for your root domain (i.e. https://your-domain.org) click disable on the right. The domain status in the AWS Amplify console will say Available (with blue dots). Wait until the status changes into a green checkmark. Click again on Manage Subdomains and enable the root domain again. Wait until the status changes again into a green checkmark.
Go to the AWS Route 53 host zone. A new record
your-domain.org A xxxxx.cloudfront.net.
was added which is the ANAME / ALIAS record for your root domain to point to the AWS Amplify app at xxxxx.cloudfront.net.
I have an issue, or perhaps an understanding problem with linking my domain with AWS. I will use the xy.ro domain as an example.
I have the xy.ro domain registered with easyhost.com. On AWS I have a node.js express web app.
My xy.ro domain is not working as it does not point to anything.
I tried to create a hosted zone on AWS with the xy.ro domain and tried to create a dataset for this domain but it does not work.
I tried to find step by step instructions also on AWS and other providers but I did not find anything.
Can someone point me into the right direction?
If your domain xy.ro is registered with easyhost.com then it would presumably also be using their DNS hosting service to serve your DNS records.
Creating a public hosted zone in AWS won't affect the DNS resolution unless you can migrate your name servers to use Route 53.
I was not able to see steps from easyhost.com website, however from the AWS side take a look at this documentation.
You should be able to copy the name servers and update within easyhost so that it will use Route 53 as your DNS provider instead.
I had a static page on aws with a custom-domain.com and everything worked fine. Then, I wanted to use that domain for another site deployed on Heroku. I neeeded to unbound the domain from aws, intuitively I just deleted the buckets from the aws console. Now I have:
404 Not Found
Code: NoSuchBucket
Message: The specified bucket does not exist
I contacted domain provider company. In their answer I identified, that the domain name uses aws DNSs, but not heroku. They also added that all the changes should be made in aws, unfortunately I do not have the buckets to work with.
What should I try to do next? I can buy another domain (it is not sufficient), but it will mean that I am defeated. I want to win, will you help me to conquer the "web bug"?
When Setting Up a Static Website Using a Custom Domain, the following configurations are made:
A bucket is created with a name name matching the domain (eg custom-domain.com)
Static Website Hosting is activated on the bucket, which provides a DNS name (eg customer-domain.s3.amazonaws.com)
A DNS entry is made in Route 53 or another DNS service that is a CNAME record pointing to the DNS name of the static website
Since your configuration was working, we can assume that all the above configurations had been made. Then, when you deleted the bucket, the domain name kept pointing to S3. With no bucket to display, S3 gave you the NoSuchBucket error.
If your intention is to point custom-domain.com to a different service (eg Heroku), you will need to modify the DNS entry for that domain name:
If your domain name is hosted by Route 53, go the the Route 53 management console, find the domain and enter a new CNAME or IP address
If your domain name is hosted elsewhere (eg GoDaddy), go to their control panel and enter a new CNAME or IP address
Bottom line: You want to change the DNS entry.