Error adding custom domain in Github pages - dns

I purchased a custom domain from Hostinger, but I am having the following error when trying to add it to my website using github pages:
"Unavailable for your website because your domain is not properly configured to support HTTPS"
I already configured the DNS as the documentation asks
It's been a few hours since I set up the domain, is there a minimum time?

Related

Custom domain for Github pages with Godaddy (.FR) is not working,

So I bought a domain which is souterrains-bapaume.fr and I am trying to link it to my Github pages website.
This is all my records:
Godaddy records here
I set the custom domain on Github pages as well and I keep getting the same page:
This site can’t be reachedwww.souterrains-bapaume.fr’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
I have another website with another domain with an extension of .me and all work perfectly with the exact same records so I am not sure what I am doing wrong.
It seems your domain was not properly configured or not successfully registered.
The .fr root zone can not found your dns. You can use dig and whois command to check.
Dig result:
souterrains-bapaume.fr:
enter image description here
google.fr
enter image description here

Azure URL is not working for the new CNAME entry

Recently we have created a new CNAME entry for the internal react website which is deployed in Azure. It has been pointed to traffic manager since we are deploying in two regions. After the CNAME entry is create, the URL throws 404 error. We have already configured the entry access restriction to all internal users. Appreciate if anyone can help to identify the issue.
For the error, you could add the new CNAME subdomain to your app service---custom domains---add custom domain as the picture displaying steps 1-5. After you validate the subdomain and add the subdomain into the custom domains, you should access the subdomain URL via the traffic manager. Read this blog for more details.
In addition, only Web Apps at the Standard SKU or above are eligible for use with Traffic Manager. Attempts to add a Web App of a lower SKU fail. Read Azure web apps as the endpoints.

Setting up an email while hosting on Netlify

Wondering if anyone has experience setting an email while hosting a site with Netfliy? I registered a domain name using google domains and pointed the name servers to Netlify that is hosting a Gatsby static site. I would like to set up an email on a shared hosting account (I’m using hostpapa).
The Netlify DNS is set up and the site is live. I have tried adding setting the A records to the hosting IP, and MX records to mail.domain… to Netlify DNS and Google Domain records... I guess the questions might be where should the name servers point first... In both cases, the nameservers are still pointed to Netlify where the site is hosted and I get the following error:
Please transfer the domain to this servers nameservers or have your
administrator add one of its nameservers to /etc/ips.remotedns and
make the proper A entries on that remote nameserver.
For setting up an email when using Netlify nameservers (DNS zone), you have to follow the instructions provided by your email provider.
This typically requires you to enter MX records into the DNS zone on Netlify. If you're using GSuite, go to "Synthetic Domains" on the google domains site and copy everything in there to the DNS zone of Netlify. You can ignore the warnings saying that you have to use google's names servers. As an example, this is my setup for email provided by GSuite:
I use Yandex.connect and Netlify make my personal mail service.
You can check the official doc. https://yandex.ru/support/connect/dns/mx.html?lang=en
Or see my steps:
register a Yandex.connect account
https://connect.yandex.com
set Domains on Yandex
set DNS on Netlify

Configuring Google Domain to point to Azure website

I have an site hosted on Azure that I am trying to point a domain from Google Domains to.
My current configuration is as follows:
Name Type Data
# A XXX.XXX.XXX.XXX
www CNAME history-podcasts.azurewebsites.net
awverify CNAME awverify.history-podcasts.com
I am following the instructions from here: Configuring a custom domain name for an Azure Website.
When I go to the Azure portal to Manage Domain and attempt to enter the url in DOMAIN NAMES, I get the following message:
A CNAME record pointing from history-podcasts.com to history-podcasts.azurewebsites.net was not found. Alternative record awverify.history-podcasts.com to awverify.history-podcasts.azurewebsites.net was not found either
When I go to the URL for the domain, I get the following message:
The website you have attempted to reach is not available in this Microsoft Azure Web Sites region. This could be due to one of several reasons:
The web site owner has registered a custom domain to point to the Microsoft Azure Web Site, but has not yet configured Azure to recognize it. Click here to read more.
When a site owner wants to use a custom domain with a Microsoft Azure Web Sites website, Azure needs to be configured to recognize the custom domain name, so that it can route the request to the appropriate server in the region. After registering the domain with a domain provider and configuring a DNS CNAME record to point to the site's Azurewebsites.net address (for example, contoso.azurewebsites.net), the website owner also needs to go to the Azure Portal and configure the site for the new domain. Click here to learn more about configuring the custom domains for a web site.
This is the same configuration settings I am currently using for several domains through Namecheap with Azure hosting and they work as intended.
EDIT:
To summarize, here are the steps you need to take:
1) Create CNAME record redirecting user from your domain to Azure specified domain using tools provided by your DNS hosting service
This step will ensure that when going to www.history-podcasts.com user will transparently be taken to history-podcasts.azurewebsites.net
Type: CNAME
Name: www
Value: history-podcasts.azurewebsites.net
IMPORTANT: Please note that it takes time for DNS servers to update their records therefore you should wait around 30 minutes before continuing.
2) Redirect your naked domain to subdomain using DNS hosting service tools
This step will ensure that when going to history-podcasts.com user will be redirected to www.history-podcasts.com
For Google Domains you can follow this guide here.
3) Add your domain to Azure Website
This step will assure Azure that you own the domain and you want your site to be reachable using specified domain name.
Login into https://manage.windowsazure.com/
Navigate Websites -> [Your Website] -> Configure
Scroll down to Domain names
Click Manage Domains (note that custom domains can only be used when in the Shared, Basic, or Standard modes)
Add your domain www.history-podcasts.com
At this point you should be able to reach your web site using both history-podcasts.com and www.history-podcasts.com domain names.
If your website requires HTTPS, you will have to take extra steps:
http://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/

How do i connect my windows azure website with my domain name perfectly?

I did almost everything that have described in the azure documentation briefly.
My domain names that i need to be assigned with my azure website url idaa.azurewebsites.net are mostout.com and www.mostout.com.
When trying to enter my site using any of the links added here, the site loads and works perfectly as i need.
But the problem is with my url which is getting loaded in browser url field while giving mostout.com or www.mostout.com.
It comes with the azure website url every time. What do I do now to get it working?
Make sure to set the CNAME for your service: have the www. name point to the full azurewebsites.net address.
Note that you'll:
need to have a level of service that supports custom domains with Windows Azure Web Sites,
add the CNAME from your www. domain to the azurewebsites domain (same goes for having the naked domain name via an A record or similar)
add the verification names, awverify.www.yourdomain.com and awverify.yourdomain.com
use the Manage Domains function in the portal for the web site to customize that domain name,
Things should just work then.

Resources