I have deleted a distribution from AWS CloudFront and trying to create a new distribution using the CNAME that I had used in the deleted distribution. I am now getting Status Code: 409; Error Code: CNAMEAlreadyExists;. I am confused because I have just deleted the distribution and I do not have any other distribution in my CloudFront. I am wondering what I am supposed to do to create the distribution again using the older CNAME.
I had the same problem. In my case, I've just deleted the old CNAME DNS from my DNS provider which was pointing to the old CloudFront link.
Related
Error creating Custom Domain in Azure
Hi, I am trying to link a custom domain to my static website that is located on my blob storage account. When creating the custom domain these are the azure instructions "Create a CNAME record with the DNS provider that points the domain (eg, www.contoso.com) to blobstorage.blob.core.windows.net or blobstorage.z13 .web.core.windows.net and then specify your domain. This method is simpler, but causes a short downtime while Azure checks the domain registration. "
In my godaddy account I have created a new CNAME record as follows Type: CNAME, name: www.mydomain.com, value: blobstorage.z13.web.core.windows.net.Y when trying to specify the custom domain in azure (mydomain.com) generates the following error: "Could not update storage account 'XXXX'. Error: The custom domain name could not be verified. CNAME mapping from mydomain.com to any of ..... does not exist "
I do not understand what I am doing wrong, I am very new in the subject and I really appreciate the help you can give me. Thank you very much
Be sure you have the CNAME record set correctly in the DNS settings for your domain name, then give it some time to update. DNS doesn't update immediately, it can take some time for the update to sync through all the DNS server between your registrar and Azure or your local ISP. This is especially the case when you test and it fails, then you need to wait at minimum the TTL (time-to-live) time that is set on the DNS records updated before you'll be able to test again.
On an aside, I'd recommend setting the TTL on the DNS records to 1/2 hour, then when everything's working you can go update it to a longer TTL. This will help when you need to update things and retest again to get it working.
I could already make the configuration I was looking for by configuring a CDN. this is the link learn.microsoft.com/en-us/azure/storage/blobs/… Thanks everybody fot your answers and comments –
I followed the steps on creating sub-domain via Route53 by creating a new Hosted Zone for cdn.domain.com and added the NS to the registrar in addition to the root domain, domain.com NS.
I then added Alternate Domain Name in the CloudFront Distribution that reads cdn.domain.com and saved it. I then waited for the status to get deployed.
My question is,
Do I still need to add an A record for the sub-domain that I created? If so, where will it route?
If I don't need to create an A Record, shall I add a new record CNAME on the root domain Hosted Zone or on the sub-domain Hosted Zone? Because I see no target Available.
IPV6 is also enabled on the CloudFront Distribution. Please advise on what would be my next step.
Thank you!
I'm not familiar with the method of multiple hosted zones for the same domain, be sure to use the correct NS servers. (see here)
The simple approach is to on the root domain add an A record for the subdomain, with an alias set to the CloudFront distribution.
Our website mywebsite.com is currently managed by Wix DNS. We wanted to create a subdomain api.mywebsite.com to forward requests to aws api gateway. Here are the steps I tried
Created an ACM certificate for *.mywebsite.com
In AWS console API gateway I created a custom domain and associated it with ACM certificated I created about. I got a cloudfront target domain name somecloudfrontid.cloudfront.net
I created a CNAME record in wix that points api.mywebsite.com to somecloudfrontid.cloudfront.net.
But, when I tried to hit api.mywebsite.com I get this error:
ERROR
The request could not be satisfied.
Bad request. Generated by cloudfront (CloudFront)
Am I missing any step? How can I get this working? Do I need to transfer my domain to AWS router 53 to make it work with AWS?
I suggest transferring the domain to Route53. There you can create an alias for your subdomain under Hosted Zones, and point it directly to your cloudfront target domain, as well as several other AWS resources quite easily.
I have an instance of openshift origin on digital ocean. Everything is working but when I create new apps it become a pain with DNS records. If I create a new domain, (php-test.openshift.example.com), the DNS record is not added to the zone file for the domain on Digital Ocean so when I try to access it I can't get anything. My solution so far has been to add the url to my /etc/hosts/ just before creating it and everything works fine but this is annoying. My question is has anyone run into this issue and how did you solve it? Did you have to make your openshift server be the actual nameserver for your domain (example.com) or were you able to hook it up to the digital ocean api using some kind of hooks system?
The default install expects that other hosts will resolve application fqdns using the installed DNS server.
To publish to an external DNS server, you will need to configure a DNS plugin, the nsupdate plugin configuration is documented here: http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#configure-the-dns-plugin
There is also a route53 plugin (source code: https://github.com/openshift/origin-server/tree/master/plugins/dns/route53)
You could also create your own custom DNS plugin by using the nsupdate plugin as a template.
For the last two days I've been unable to create a CNAME from my domain to my blob storage account. I've registered the domain and added a CNAME that points to verify.azure.com on my DNS settings, but whenever I validate it (even after waiting a few hours), it never seems to validate... the error I get the Azure portal is "An unexpected error occurred while validating the domain name. Try again later."
Are there some issues going on?
verify.azure.com will only authenticate that you have the proper key to your domain however you would need another alias to set the proper CNAME configuration. Based on what you have written above you are pointing your host to verify.azure.com, however have you setup your storage subdomain alias to your storage name as well? If you have setup both the entries correctly, and still see the problem, at your domain registrar level there are some logs available which you can request for further troubleshooting.
Get more info here and here.