I am working on setting up a custom domain for a GitHub pages website and I have everything set up but on GitHub pages settings with the A records and CNAME records.
But, I have the following error;
ekenestan.com is improperly configured Domain does not resolve to the GitHub Pages server. For more information, see Learn more (NotServedByPagesError). We recommend you add an A record pointing to our IP addresses, or an ALIAS record pointing to ivory222.github.io
Please help:
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.
This might look like a duplicate but i can't seem to find the answer to this question on other similar threads.
I've been trying to verify my custom domain on gitlab pages but it keeps giving the 'failed to verify domain ownership' error. My DNS settings are set like this. On gitlab i've added the domain in the settings/pages tab.
When going to the domain now, it only shows a gitlab 404, which is the exact same as just entering '52.167.214.135' in the address bar. I've waited a few days for the verification.
What am i doing wrong, and how can i fix it?
(Note: The TTL of 1min is only temporary for testing purposes)
The Gitlab documentation for setting a personal domain is wrong. If you want to set to your page the www.foo.bar subdomain Gitlab give you this entries to add in your DNS file.
www.foo.bar CNAME free_zed.gitlab.io.
_gitlab-pages-verification-code.www.foo.bar TXT gitlab-pages-verification-code=776615a3e132b0f5a6638c7e26e59084
This cannot work, you had to use these entries instead :
www CNAME free_zed.gitlab.io.
_gitlab-pages-verification-code.www TXT gitlab-pages-verification-code=776615a3e132b0f5a6638c7e26e59084
See Gitlab pages issue
I've got an organization page set up and running in GitHub and things seem to be working...but I'm a little confused. I'd like to actually understand the process since the GitHub Help article refers to taking advantage of their CDN and DoS services, so bear with me.
Step 1: Created CNAME file in repo with domain 'example.com'
Step 2: Grabbed IP from dig example.github.io +nostats +nocomments +nocmd
Step 3: Entered IP from Step 2 into the 'A' record (see image below)
I decided to stop here and see where it got me, and to my surprise it seems to have done the trick. The example.github.io domain correctly redirects to the example.com domain and displays the content from the repo.
However I was informed that after the DNS props, you can dig example.com and see the CNAME record pointing to example.github.io. I do not see this, and I dislike thinking that I didn't set things up correctly. Any thoughts/comments/tips welcome, thanks!
In order to take advantage of the CDN and DoS services provided by GitHub Pages, you'll need to set up a Subdomain (eg www.example.com or blog.example.com) instead of an Apex domain (example.com).
From the GitHub Help page you referenced:
If you are using an apex domain (example.com) instead of a subdomain
(www.example.com) and your DNS provider does not support ALIAS
records, then your only option is to use A records for your DNS. This
will not give you the benefit of our Content Delivery Network.
Here's a setup (looks like you're using GoDaddy for DNS) that would work to get your Organization Pages working as desired:
This is actually for a Project Page within an Organization, but for either one, you'll set the CNAME record for www to organization.github.io, not something like organization.github.io/project. Don't change the A record for # (mine is the default from GoDaddy).
If you want to get your Apex domain (example.com) to redirect to the new subdomain (www.example.com), then you can point your Apex to your subdomain with Domain Forwarding like this:
With that setup, you'll get to take advantage of GitHub's CDN, which you may notice is provided through fastly. Here's how my domain looks to dig:
It is also possible to use a CNAME record for an APEX domain using the free DNS service provided by CloudFlare in which case you can also use your domain without the www (or any other subdomain) and still benefit from CDN & DoS.
I've written a step-by-step guide here: Speed up your GitHub Pages website with CloudFlare
PS: Apparently using ALIAS records is a bad idea... click here to see why.
DNS records are publicly available. There's no way of masking them in this instance. From the way you describe it, you have done everything right. There is nothing that makes me thing you set this up incorrectly.
I am trying to map my site which is on github pages (tusharmath.github.io) to a particular domain (tusharm.com) using cloudflare name servers.
Its been more than a day and i can still not see view my website on tusharm.com
Steps followed -
Added a CNAME file with value tusharm.com in the gh-pages branch on github.
Updated name servers on CrazyDomain that were provided by CloudFlare.
tusharm.com is loading the same content as tusharmath.github.io at this time, which would lead me to believe you were able to fix things here. Did you need to make any further changes to get this working?
p.s. I work for CloudFlare.
I'm attempting to satisfy the Cookieless domain suggestion of Google's Page Speed plugin and am running into a wall with my host who can't be bothered with the details of why it's not working. Accessing st1.dgcstatic.com should be the same as accessing st1.defunctgames.com; however, this is not the case.
Have I missed a step of configuration? Do I need to wait for DNS propagation? You can see below my steps of experimentation.
DNS Setup:
Created CNAME of st1.dgcstatic.com to point to st1.defunctgames.com on dgcstatic.com
Created A record of st1.defunctgames.com on defunctgames.com
Created sub-domain of st1.defunctgames.com on defunctgames.com
When I run a tracert st1.dgcstatic.com it produces the following result:
C:\Users\Patrick>tracert st1.dgcstatic.com
Tracing route to st1.defunctgames.com [50.22.11.10]
When I run a host st1.dgcstatic.com it produces the following result:
patrick:~ patrick$ host st1.dgcstatic.com
st1.dgcstatic.com is an alias for st1.defunctgames.com.
st1.defunctgames.com has address 50.22.11.10
And finally, using this site it seems to produce the same results of showing things configured correctly.
http://www.mxtoolbox.com/SuperTool.aspx?action=mx%3ast1.dgcstatic.com
According to all these results, the world can see my DNS changes, my host on the other hand gave me the "Wait for propagation" rigmarole When asked why this isn't working.
It looks to me that your domain names are set up correctly (st1.dgcstatic.com is an alias of st1.defunctgames.com), but the web host needs to have a mapping or configuration to know how to serve st1.dgcstatic.com content.
Both domains are resolving to 50.22.11.10, but that is most likely a shared IP address host. (Visiting http://50.22.11.10 demonstrates that it's shared - it can't resolve to your site just by the IP address.)
You'll need to configure through your webhost provider the second domain. Hosting companies do this differently; in my case it's just a matter of adding a new domain to my account (extra $1/mo), and configuring the path for HTML source files.