I have a page up at amongmany.github.io and I have followed the instructions here for a custom domain. I made those changes roughly 16 hours ago. Now, I know that DNS records "can take up to 24 hours" but in my experience it never does. So I'm trying to confirm that I've set things up correctly.
Here are my DNS settings and I have added the CNAME file to my project which appears to be working as amongmany.github.io is redirecting to 1amongmany.com already.
Am I doing something wrong?
Something's missing from your information:
root#ent01:/etc/bind# dig +noall +answer amongmany.github.io
amongmany.github.io. 3547 IN CNAME github.map.fastly.net.
github.map.fastly.net. 23 IN A 185.31.17.133
root#ent01:/etc/bind# dig +noall +answer 1amongmany.com
1amongmany.com. 1789 IN A 66.6.44.4
There is a 301 redirect from http://amongmany.github.io/ to Location:http://1amongmany.com/. However, your www returns a 404, and does not appear to be resolving to the addresses above:
root#ent01:/etc/bind# dig +short www.amongmany.github.io
github.map.fastly.net.
185.31.17.133
I guess I'm still a little confused as to what result are you trying to achieve?
Related
Hey so How to setup CNAME DNS for www to point towards the root domain. The Root cname works but the www CName doesn't. i have it like the this
I have my react page hosted on Cloudflare pages, but when I go to https://www.stron.ml It returns the following error. I am kinda new to web hosting stuff .
Error 523
Ray ID: 650b0c9bcc380b97 • 2021-05-17 07:14:30 UTC
Origin is unreachable
I tried even adding a subdomain like dev. but I got the same error ,
Thank You
at the moment your redirection seems working, it could've been simply a matter of propagation time.
Anyway, keep in mind that pointing a CNAME to another CNAME is discouraged by the official RFC, so pointing your www subdomain to stron.ml, while stron.ml is already a CNAME should be avoided:
Don't use CNAMEs in combination with RRs which point to other names like MX, CNAME, PTR and NS.
I am trying to host a website, I changed to Name servers and all, however I am receiving this error
The webserver reported that an error occurred while trying to access the website. Please click here to return to the previous page.
Can some body help me on this?
Thank you
First ensure that the domain is resolving to the IP's you configured, for this you could use tools like dig / drill, or via the web you could use https://intodns.com/
To check the nameservers via command line:
$ dig example.com ns +short
To check for the 'A' records:
$ dig example.com
If you just change the nameservers it may take a while for them to be replicated, you can use the +trace options:
$ dig example.com ns +trace
When tracing is enabled, dig makes iterative queries to resolve the name being looked up. It will follow
referrals from the root servers, showing the answer from each server that was used to resolve the lookup.
If that returns the expected results, check your web server configuration.
I previously had my GitHub pages site set up correctly with my custom domain and my Cloudflare DNS, however, I was playing around with my CNAME records but decided I wanted to revert back to how things were before.
I set my CNAME records to what they were previously, however, when I go to my custom domain I get the error.
Error 1014: CNAME Cross-User Banned
Never seen this error before, how can I fix this. Screenshots of settings attached
GitHub
Cloudflare
This is solving it for me.
https://twitter.com/stefanprodan/status/834872543790174209
#stefanprodan -
1:08 PM - 23 Feb 2017
If you use #Cloudflare with #Github pages change your CNAME to
http://github.map.fastly.net to fix Error 1014 CNAME Cross-User
Banned
I have my domain example.com on CloudFlare and a subdomain, fo.example.com, delegated to another name server.
This is the setting on CloudFlare
A www.example.com 1.2.3.4
CNAME test www.example.com
CNAME test2 www.google.com
CNAME test3 fo.example.com
plus the NS for fo. All the above have the orange icon, i.e. requests should go through CloudFlare.
and this is the setting on the other nameserver
A fo.example.com 5.6.7.8
Now, when I traceroute www.example.com, test.example.com and test2.example.com I can see that it goes through CloudFlare but when I traceroute test3.example.com it goes direct exactly as I traceroute fo.example.com. This looks incorrect to me, why requests to a CNAME pointing to an extrenal domain (google.com) goes through cloudflare and the one pointing to a delegated subdomain does not?
Very difficult to look at without knowing the actual subdomain in question. There are some records that can't be proxied (pointing to other CDNs, for example, does create DNS lookup issues in some cases).
CloudFlare supports answer:
That's not possible, no way around it either. I've tried.
Unfortunately our current system doesn't allow this. This has been a
feature request for awhile, it will get added eventually, but no ETA
as of right now, sorry.
I am using the Alternc control panel for shared hosting.
I am setting up a subdomain to point to github pages, as described here.
I need to point the CNAME record for my subdomain to .github.io, which I did with the alternc interface as seen in this image.
After waiting more than 24 hours, I got this message from github:
CNAME record should point to `your-username.github.io`, but it does not.
In effect, when visiting http://mxtoolbox.com/SuperTool.aspx?action=cname%3asommet.terredesjeunes.org&run=toolpage#, the CNAME record seems to be set to:
alberto56.github.io.terredesjeunes.org
not
alberto56.github.io
Same thing when running dig:
$ dig sommet.terredesjeunes.org +nostats +nocomments +nocmd
...
;sommet.terredesjeunes.org. IN A
sommet.terredesjeunes.org. 86400 IN CNAME alberto56.github.io.terredesjeunes.org.
I would be expecting to see the CNAME being alberto56.github.io, not alberto56.github.io.terredesjeunes.org. Is this a glitch with alternc, or am I not understanding something?
Thanks!
Albert.
Full DNS names need to end in a ., the root zone, otherwise the current zone is appended to the name. So, you want to set your CNAME to alberto56.github.io. with the terminal period to indicate that resolution should start from the root zone.