I'm following the top answer to this question: Custom domain for GitHub project pages to upload my github page into my custom domain. I'm using cloudflare as my dns. I first added the four A records without a problem, but then i try to add the CNAME record and i'm getting an error saying that there is already a record with that host, should i ignore the CNAME? Or what should i do? If i upload first the CNAME record and then the A records i get the same problem. I'm uploading the CNAME as the root in the name and myname.github.io in the target.
Related
I have a domain that I got from NameCheap: www.app.flerr.io.
I configured the domain in AWS with Route53, CloudFront and S3.
I uploaded the static website to the relevant S3 bucket.
When I try to reach my website, I get the following error: ERR_NAME_NOT_RESOLVED.
Although, when I reach the website through S3 static website hosting it's working:
Any ideas?
EDIT:
Route53:
I have one A record that traffics to <id>.cloudfront.net:
I have one NS record that traffics to 4 NS URLs.
I have one SOA record.
I have one CNAME record.
ERR_NAME_NOT_RESOLVED usually refers to a DNS problem.
You already verified that S3 URL is working correctly.
Now, verify that Cloudfront is working correctly by pasting the Cloudfront URL in your browser (<id>.cloudfront.com or something similar).
If both of them are working, means that your problem is indeed DNS (and therefore Route53) related.
Use any DNS Lookup page to see if your domain (flerr.io) is correctly set up.
https://mxtoolbox.com/SuperTool.aspx?action=a%3awww.app.flerr.io&run=toolpage
With the information given that's the best we can do, if you share your Route53 Hosted Zones we could see if anything is wrong
If you bought flerr.io. - you dont need to create a new zone for app.flerr.io. (you can, but its not required - this is called DNS delegation). You just need to create a record named www.app inside flerr.io. as an A or CNAME to your destination.
When i use dig to test the DNS i get the following results:
dig flerr.io. shows A records
dig app.flerr.io. shows A records - and appears to be its own DNS delegation zone (was that deliberate)?
dig www.app.flerr.io. does not return any records - this is why you cant resolve your site.
I think the solution for you is to create the www.app records in the flerr.io. zone and ignore the app.flerr.io. zone you created. If your trying to use the zone app.flerr.io. (and its been setup properly in flerr.io.) you would just create the www record.
I've got 5 records in my AWS Route 53 hosted zone:
First is an NS for my domain name.
Second is SOA for that domain.
Third is a validated CNAME for it.
Fourth is cloudfront distribution A alias for it with the www prefix.
Fifth is validated CNAME for the www version.
I don't yet have an SSL attached to it.
It works - well partially.
Trying to reach the unprefixed version of the domain from Chrome doesn't work, but if I type the domain with the www prefix it works.
Firefox automatically redirects the unprefixed domain to the www variant. I type the unprefixed name making sure it's not redirecting because the prefixed name is in the search history. When I hit enter, Firefox automatically redirects to the www.
I'd like the main name to be accessible, not just the www one. It's OK if someone types the www. They should get to the site, but the actual name has no www.
I'm inexperienced enough not to be certain about that www prefix or why it is necessary. This was the result of a long course on AWS services.
Can anyone tell me if I'm missing a needed record, or if I'm improperly using the Alias A record?
Edited to add this below after reading first three answers. Thank all of you who answered for your responses. I do appreciate them. Please see my comments on those answers. --
I'm attaching a screenshot of my Route 53 hosted zone settings to maybe help you get a clearer picture of where I am.
Please remember. I'm not starting with a domain with a site that I wanted to host on S3 and then redirect www.mydomain traffic to mydomain.
I began coding an app with no domain. Then I uploaded it to an S3 bucket. I then was able to access it's simple S3 hosting with the ugly url. Then I used CloudFront for a world-wide distribution, again with an ugly url. Only then did I try taking one of my owned subdomains and redirecting it to Route 53. It wasn't as clean and simple as buying a domain from Amazon. I had no SSL and had to make a request for the AWS Certificate Manager to process validation of my domain. I got all that.
My problem is as I tried to explain - Chrome won't recognize or redirect my main domain name without the www. It only recognizes if one types the www. in front of the domain name. On the other hand, Firefox automatically redirects no matter what you type (the www version or the one without the www). That redirection is to the www version (that is what shows in the url bar in the end - http://www.mydomain).
I think I may have figured out most of this. As I mentioned in my comment above, I noticed I didn't have an Alias record for my main domain. I also read in AWS documentation that my S3 hosting bucket should have the same name as the domain, so I did that.
After creating the new original S3 hosting bucket I had made another to keep the log files. I set up a CloudFront Distribution. Then I requested and got SSL certificates for my owned domain name and added another for the www version. With those successfully enabled, I transferred my registered DNS servers to AWS. That created the NS and SOA records when I created my R-53 hosted zone. I then created Alias records for both the man and www version and added the validated SSL certificates for both the main domain and the www version. So, a total of six records in the zone.
I created my new S3 bucket, naming it the same as my domain; copied the settings from the old one, set it up to host static single page site and generate logs. I had already created a bucket for the logs, so I just pointed the logs location for the new domain named bucket. I gave the regular logs a log prefix (folder) and the CloudFront logs a cdn one.
Everything works great except I discovered a new problem. I'll post a new question regarding that, something like XML error on browser refresh in child pages.
Thanks ALL!
I want to make a custom domain for project documentation in postman. I added a TXT record and CNAME in the DNS section of Cloudflare. But when I click on the Verify Domain button, an error appears: Something went wrong No CNAME record found for this domain.
This is from cloudflare side:
When a CNAME record is orange clouded we basically treat it like an A record AND cloudflare obfuscate the origin and just return the IP address. As a result if you do a DNS query for CNAME with an orange clouded record you won’t see it (but an A record query will return the destination IP).
For services which are looking to validate with a specific value obfuscation = bad. So to prevent this you’ll want to make sure the record is :grey: not :orange:.
I've got a web applicaiton set up on elastic beanstalk. I've a domain on route53, and I've followed the guides more or less here:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html
The URL to the webapp works fine, but the DNS is not pointing me to it.
To be honest, I'm not sure where to even begin looking at how to fix this. I've tried to use the 'Check response from Route 53' feature and I can't see anything out of the ordinary. I've attached a lot of pics.
Any idea?
Please see here for the images, I couldn't upload them here. I kepy getting format errors.
http://imgur.com/a/NwCbb
******update*******
Updated, new hosted zone configuration:
******update*******
The name is still not resolving. I've added an A type record set and selected the elastic beanstlak as the alais.
******Answer*******
Credit to imperalix for this.
Amazon registered the wrong name servers for my site.
I needed to go to
https://www.whois.net/
and search for my www.thetellyourstory.com
I got the values for my name server there:
Name Server: NS-1487.AWSDNS-57.ORG
Name Server: NS-187.AWSDNS-23.COM
Name Server: NS-1891.AWSDNS-44.CO.UK
Name Server: NS-802.AWSDNS-36.NET
Then, go into route 53 and update the name server values:
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
It's important to update the name server values only as above. You can edit them directly from http://imgur.com/a/a41z2 here but it does not update the values.
It looks like your registrar, Amazon, has the wrong name servers configured [1]. I compared your whois information with your screenshot. I would recommend updating your name servers[2] for your domain to match what your zone has configured.
Update your registrar to (this is from your screenshot of Route 53 DNS):
ns-1487.awsdns-57.org.
ns-187.awsdns-23.com.
ns-1891.awsdns-44.co.uk.
ns-802.awsdns-36.net.
Your Route 53 DNS configuration look fine[3].
$ whois thetellyourstory.com
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html
http://digwebinterface.com/?hostnames=www.thetellyourstory.com.&type=&useresolver=8.8.4.4&ns=self&nameservers=ns-187.awsdns-23.com
Change the NS record to just tellyourstory.com, i.e. remove the "www." from the name value.
Delete the CNAME record with the name cname.www.tellyourstory.com
Change the A record www.tellyourstory.com to a CNAME record. This record doesn't need to be an alias. It just needs to have the value of your elastic beanstalk app.
How long ago did you register this domain name and create these records? For a new domain name it can take 24 hours or so for DNS records to start resolving.
I have an EC2 server. I want to connect it with my Godaddy domain.
This is what I did till now:
I have a domain signed on Godaddy.
I have an EC2 server with a website running on it.
I defined the domain on Route 53 (created a "Record Set" that is: example.com):
Created a new Record Set for MX (which is very important for me!)
Created a new Record Set IPV4 that uses the Public IP of my EC2 server as a value).
Pasted the 4 DNSs from the NS Record Set row on my Godaddy account instead the existing standard ones.
http://i.stack.imgur.com/POLUc.png
Results:
My website loads as: example.com - Check!
I get Emails (myname#example.com) without any problems - Check!
The Problem: My website doesn't load when running 'www' before the domain: www.example.com
I was googling for some answers and found a lot of ways to handle domains. Some of them were even very strange (like pointing to other IP addresses which doesn't answer my question), and some were very simple that work only with static content with the S3.
Bottom line questins:
What is the normal best way to make an external domain (from Godaddy for this case) link with my EC2 server + MX working + getting the website loading with or without the 'www' ?
** It must be without creating a 'www' sub-domain for - SEO reasons.
I hope my question is well explained.
If not please comment and I will edit and add information/PrtScns.
I don't think this has anything to do with DNS.
Your webserver is probably using Virtual Hosts and isn't configured to serve the site on www.example.com
If its Apache try:
ServerName example.com
ServerAlias www.example.com
(presuming of course that a DNS record exists for www.example.com)
just create an A record with www (www.example.com) and pointed to the EC2 IP
Change your current functioning redirect to include the WWW, then follow these steps:
I just managed to figure this out yesterday:
Go to you S3 console at https://console.aws.amazon.com/s3/home and click Create Bucket. For Bucket Name enter in your naked domain name, eg for www.example.com, you would put just example.com.
Click on the magnifying glass icon next to your newly created bucket. On the menu that appears select Static Website Hosting, then click on 'Redirect all requests to another host name'. The textbox that appears should now be prepopulated with the text www.example.com. Select save.
Open your Route 53 hosted zone at https://console.aws.amazon.com/route53/home. Select your domain and click on Create Record Set. Leave the Name area blank, and leave the default type at 'A - IPv4 address'. Select Yes for Alias, and click on the Alias Target textbox. At this point a dropdown menu should appear in which you can select the S3 Website Endpoint you created in steps 1 and 2.
Lastly, click create, and enjoy your new routing set-up!