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
Related
There seems to be a conflict between the DNS settings SquareSpace needs in order to set up a connection to the SquareSpace Analytics Search Console and what DNS settings Ionos will allow.
On Square Space the relevant setting are found at Home > Analytics > Connect followed by logging in with a gmail account and then clicking on Allow. At which we get the error message
Something went wrong
Sorry, something went wrong there. Please try again
I raised a query with SquareSpace and their response boils down to
There's one DNS record missing. You'd need to go into your domain's
DNS settings in your domain provider's end and then add the following
record:
Type: CNAME
Host: www
Points To: ext-cust.squarespace.com
Over to IONOS where the domain is registered and into the DNS settings which are currently
MX # mx00.1and1.co.uk
MX # mx01.1and1.co.uk
TXT # "v=spf1 include:_spf.perfora.net include:_spf.kundenserver.de -all" -
CNAME _domainconnect _domainconnect.1and1.com Standard Record
CNAME autodiscover adsredir.1and1.info Standard Record
A ftp 198.185.159.144
and attempt to add a new record as per SquareSpace's instructions above, only to get the error message
A CNAME record can only be set for a subdomain. To alias your main domain please use Redirect
But looking at redirect I'm worried that, if I set this up, all the email addresses that use the same domain and Ionos' mail servers will fail. I seem to remember trying this exercise about 2 years ago, but managed to kill everyone's email accounts (!) until I removed it again.
Has anyone had this problem and solved it? It seems specific to SquareSpace / Ionos as they both give a standard set of instructions which they expect to work.
Later
After working with Ionos' customer service desk, they managed to add the required Squarespace DNS entry and they now read
TYPE HOST NAME VALUE SERVICE ACTIONS
CNAME autodiscover.www adsredir.1and1.info Standard Record
CNAME www ext-cust.squarespace.com -
CNAME autodiscover adsredir.1and1.info Standard Record
CNAME _domainconnect _domainconnect.1and1.com Standard Record
TXT # "v=spf1 include:_spf.perfora.net include:_spf.kundenserver.de -all" -
MX # mx01.1and1.co.uk -
MX # mx00.1and1.co.uk -
A # 198.185.159.144
But the problem persists, something is still wrong when I try to attach the Google search console (AKA Squarespace Analytics Search Console -
Squarespace call it two different names in different parts of their site).
Having fixed the DNS entries to satisfy Squarespace, the "allow" error still persisted.
Squarespace customer service then suggested clearing the browser cache or using a different browser. Clearing the Chrome cache didn't work, but switching from Chrome to MS Edge did. Logging into our Squarespace account on Edge finally let the process run to completion.
I presume there must have been some information still cached in Chrome that Squarespace didn't like, I only cleared the temporary files, not the cookies or the history as I wanted to keep these for other sites.
The cause of the problem remains a mystery.
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.
Currently I have linked my website with cloudflare in order to make us of the cdn. So what I did was the following:
Changed nameservers in my hosting to the ones I received from Cloudflare
Added 2x cname & a Record to cloudflare
It is for the domainname: autobedrijfvugts.nl
Currently I am receiving a 1016 error which is a Origin DNS error. I checked the website with pingdom and the CNAMES doesn't seem to work.
Could someone help me out with this issue? It's been a day already since the site is offline..
Thanks a lot!
It appeared that the CNAME records wasn't correctly set.
It had to be set to the www.
This question is highly similar to this, but barely different:
configuring namecheap domains with heroku
Here is what I have (for the purposes of hiding the original site, I have omitted its name for the string 'asdf'):
A namecheap domain titled as follows: asdf.com
A herokuapp running on a dyno that is hobby level that also has ACM set for automatic certificate management. It is running at https://asdf.herokuapp.com/ and this link works and gets my pushes from github integration. It is awesome :)
I want to link these up so that instead of having my site as https://asdf.herokuapp.com it would instead be https://asdf.com, so that is why I went and bought the namecheap domain for it, but linking these together I have failed at every opportunity. I have tried many different patterns but unfortunately I'm unknowledged on this layer of things. Here is something I have tried, but does not work:
On Heroku: Create a custom domain of: asdf.com
Heroku then supplies me with: asdf.com.herokudns.com
I then go into namecheap, and remove any and all possible cnames or redirects.
I create a new CNAME | host: www | target: asdf.com.herokudns.com
When trying to hit the site, I get this error:
ERR_NAME_NOT_RESOLVED
If I try changing CNAME host to # on namecheap, I get:
ERR_SSL_PROTOCOL_ERROR
Any help is greatly appreciated, and if more information is needed just ask.
Thank you.
I am experiencing the same issue. I've contacted Namecheap and Heroku both for support. This is what I've come up with, but my domain is still not resolving.
Since you're pointing www.mollydwellness.org at your app, you'll need to make sure you've added that to your Heroku config (currently you only have the non-www version assigned):
$ heroku domains:add www.mollydwellness.org --app mollydwellness
Once that is added, you should receive a new DNS target that you'll need to use to update your CNAME record.
$ heroku domains
=== mollydwellness Heroku Domain
mollydwellness.herokuapp.com
=== mollydwellness Custom Domains
Domain Name DNS Record Type DNS Target
────────────────────── ─────────────── ────────────────────────────────────
www.mollydwellness.org CNAME www.mollydwellness.org.herokudns.com
mollydwellness.org ALIAS or ANAME mollydwellness.org.herokudns.com
Namecheap Config
Type Host Value TTL
CNAME Record www
www.mollydwellness.org.herokudns.com.
5 min
URL Redirect Record
#
http://www.mollydwellness.org/
Unmasked
I am told to give it another 30 minutes before contacting support again. It's been 45 minutes and still not resolving.
Very confused, probably just going to deploy it myself to a VPS because that would be easier at this point. I went with Heroku to save myself time, but it appears there can be no shortcuts. More help from the community would be great.
the only thing you need to do for dns, is going to heroku, setting the following on the custom domain :
*.mywebsite.com
mywebsite.com
www.mywebsite.com
on Namecheap you do the following configuration:
CNAME Record # myapp.herokuapp.com. 1 min
CNAME Record www myapp.herokuapp.com. 1 min
URL Redirect Record # https://www.myapp.herokuapp.com Unmasked
URL Redirect Record www https://www.aipredictor.herokuapp.com Unmasked
and you are done. that covers all of the possible scenarios.
I have a site hosted at mysite.azurewebsites.net.
I have a domain from hover.com - mysite.com - which I've configured with CNAME records per the inline instructions AND msdn documentation.
I've spoken to hover and verified on whatsmydns.com that the cname records have propagated - which they have.
Yet when I type mysite.com or www.mysite.com (I have one CNAME for each) into the azure custom domain input - it doesn't resolve, even after 24 hours of the entry being edited on hover's end (They have a 1 hour TT). I get the generic "The DNS record could not be located" error.
Images:
If I check whatsmydns for www.mysite.com, I see all dns records pointing to mysite.azurewebsites.net.
What's going on here?
If anyone else runs into this problem - I just had to wait. It took a little over 48 hours for Azure to resolve the CNAME entries from hover. It's all set now though :)