I wanted to use CloudFlare for my website (hosted on Microsoft Azure).
I have added my domain to Cloudflare, and changed my domains nameservers to the ones I got from Cloudflare.
Furthermore, cloudflare imported my current DNS settings which are the following (my domain has been replaced with domain.com):
I thought the migration would go smoothly, however, when I go to www.domain.com I get the error:
The webpage at http://www.domain.com/ might be temporarily down or
it may have moved permanently to a new web address.
However, when I refresh a couple of times it finally loads the site.
If I go to domain.com (no www-prefix), I get the error:
domain.com’s server DNS address could not be found.
What could be going on?
For the first issue...if you are seeing inconsistent responses from your Azure Website, they you should raise an Azure support ticket.
For the second issue...try verifying the CLOUDFLARE DNS resolution via http://digwebinterface.com, both via a recursive DNS service and by querying against the CLOUDFLARE name servers directly. If the latter is working, there must be a problem in your DNS delegation (check name server settings with your registrar, try also a delegation validation service such as http://dnscheck.pingdom.com/). If the latter is not working, you'll need to take it up with CLOUDFLARE.
You need both # and www CNAME specified in your host records. Not just www.
the refresh is normal after you make a dns change. The browser keeps the dns lookup in cache, so if you visit the site on another browser you won't have to do a refresh. Just clear your browser cache when you want to see dns changes, but some edits could take 15min or longer to see changes.
Related
I have static website on azure storage, it's connected to azure cdn to have https, and i have my custom domain folla.com.pl I want this domain to point to https://companywebsitecdn.azureedge.net/ which is address of my website on azure cdn. I chose custom domain on cdn configuration site, it asks me to make dns mapping to verify ownership, so i make CNAME cdnverify.folla.com.pl to cdnveriy.companywebsitecdn.azureedge.net and it get me to other window with custom doamin https config. And here's my problem, it get's stuck on second step
How I'm suppouse to configure another mapping to make it work, what i mean is to make folla.com.pl to point to https://companywebsitecdn.azureedge.net/ with https. I can't proivde what i already tried with my dns because it was a lot and i don't remember all of it. Also it's already second try and everytime after failure I have wait 8 hours for another try. Thanks in advance
This is my DNS config
When you try to add your custom domain folla.com.pl in the custom domains settings of Azure CDN endpoint. Before this step, you should have a CNAME record in the following format in the DNS zone.
When you turn on the custom domain https, you don't need to make a CNAME cdnverify.folla.com.pl to cdnveriy.companywebsitecdn.azureedge.net. Read here.
If that CNAME record still exists and does not contain the cdnverify
subdomain, the DigiCert CA uses it to automatically validate ownership
of your custom domain.
If the CNAME record entry contains the cdnverify subdomain, follow the rest of the instructions in this step.
DigiCert sends a verification email to the following email addresses. Verify that you can approve directly from one of the following addresses and read here.
admin#<your-domain-name.com>
administrator#<your-domain-name.com>
webmaster#<your-domain-name.com>
hostmaster#<your-domain-name.com>
postmaster#<your-domain-name.com>
Automatic validation typically takes a few hours. If you don’t see your domain validated in 24 hours, open a support ticket.
I've created a Google Site on my personal account and am trying to publish it to my custom URL hosted on Google Domains through that account. Per the instructions I did this using the Publish settings... dialog and entered the custom URL:
The normal sites.google.com/... URL works fine, but the custom one doesn't:
My DNS settings in the Google Domains console are pretty simple, just some G Suite mappings and what looks to be the resource record automatically populated by Google Sites:
How can I fix the DNS_PROBE_FINISHED_NXDOMAIN issue to get the site forwarded correctly?
The DNS PROBE FINISHED NXDOMAIN problem was started due to incompatibility of IP addresses with computer DNS. To be more technical, DNS converts all messages from a domain into a form of IP address. The real problem arises when someone enters a URL in their browser; it's up to DNS to find a server with the appropriate server IP address. While in the general case, the search process is directed to the target site, but if the DNS fails, this will produce an error. Changing DNS server to Google DNS or OpenDNS , or remove all cookies and cached files on your browser will help to resolve this issue immediately. Like any other error, there are several ways you can solve these problems by yourself:
Release or Renew Your IP Address
Change DNS server
Restart DNS Client service
Reset hosts file
Reset Chrome Flags
Reset Winsock program
A client of ours has the domain client.com
Our application is at superapp.mycompany.com
We want the client to be able to access our application via their own subdomain, like: superapp.client.com.
Normally we'd just tell the client to add a cname for superapp and point it to superapp.mycompany.com. Then on our server (IIS) we'd bind their domain to our app and everything would work as intended.
However, we can't replicate this functionality when our mycompany.com domain is managed via cloudflare.
When we navigate to superapp.client.com we get the following error page:
Error 1001
What happened?
You've requested a page on a website (superapp.client.com) that is on the Cloudflare network. Cloudflare is currently unable to resolve your requested domain (superapp.client.com).
Is there any way that Cloudflare can be used in this fashion?, this seems like a pretty standard set up for a multi tenant application that supports custom domains.
We don't need all the protection that Cloudfront offers for these client domains, but we want to use the Cloudfront nameservers for out application (mainly for fast switching of DNS records in the event we migrate servers, etc).
Any help is appreciated.
I hope it's not too late. But just found a way to do so.
You just need to add your client's domain (Add site in Cloudflare) to your account.
You don't need to change client domain's NS. So in your Cloudflare panel this domain will showing as "Pending Nameserver Update".
Next step is add the CName record to this domain.
Although the NS of client domain is not changed to CF, but CF has a lookup record as CName for it.
Hope it helps.
Just in case someone arrived here with same issue as me. Here is the answer. For short, no that won't work.
Since Cloudflare is a reverse proxy for the domain that is on Cloudflare, the CNAME redirect for the domain (not on Cloudflare) wouldn't know where to send the traffic to.
Ref: https://support.cloudflare.com/hc/en-us/articles/360017421192-Cloudflare-DNS-FAQ#CloudflareDNSFAQ-CanICNAMEadomainnotonCloudflaretoadomainthatisonCloudflare
If you don't need the CDN benefits, you can still use Cloudflare nameservers to manage your DNS zone and keep your current configuration. Just make sure the CDN is deactivated for the target subdomain in your zone (superapp.mycompany.com in your case).
You can tell if the CDN is activated or deactivated for a subdomain by looking at the cloud icon on the right of each DNS entry: if the cloud is orange the CDN is active, if it is gray, it isn't.
Cloudflare also supports external CNAME resolution in their CDN infrastructure, but it's only available for its Enterprise customers:
https://support.cloudflare.com/hc/en-us/articles/217371987-Managed-CNAME
A couple of days ago I set up a new site in Azure and modified my DNS records to point to the site. I am unable to add the custom domains through the management tool or the portal.
The error I see is
"A CNAME record pointing from mysite.com to mysite.azurewebsites.net was not found. Alternative record awverify.mysite.com to awverify.mysite.azurewebsites.net was not found either."
(Changed my real domain to mysite as I'd rather not put that here).
The worst part is when I visit "mysite.com" it is showing me an Azure 404 page saying "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.".. I'm trying to configure it but Azure is not letting me!!!
For my DNS i have:
an A-Record pointing to my virtual IP
a second A-Record for www pointing to the IP (I did have www as a CNAME-Record for mysite.azurewebsites.net but that didn't seem to be working)
a CNAME-Record for awverify.mysite.com to awverify.mysite.azurewebsites.net
a CNAME-Record for awverify.www.mysite.com to awverify.www.mysite.azurewebsites.net
I thought maybe it was taking forever to propagate but it's been 2 days now.
Thanks!
Although it usually takes a couple of minutes for DNS records to be available, it can take up to 72 hours for DNS records to propagate. If it is all configured correctly (and looking at the list you posted, it is), it's a matter of waiting for it to propagate.
I'm trying to verify a custom .ninja domain for a Azure hosted website, but it fails to complete verification. I've completed these steps for several other sites and domains hosted in Azure before and familiar with the awverify CNAME requirement. I've also updated the A record(s) with the Azure provided IP. A ping on the domain name returns the correct IP. It has been close to 48 hours of waiting giving plenty of time for DNS settings to propagate.
Here's the error (I replaced the actual domain with "mydomain"):
A CNAME record pointing from mydomain.ninja to mydomain.azurewebsites.net was not found. Alternative record awverify.mydomain.ninja to awverify.mydomain.azurewebsites.net was not found either.
Are there any restrictions on .ninja domains or those that do not have 3 char extensions maybe? All my other successful attempts with other sites have been on .com domains.
Added an A record for the www prefix, thus having 2 A records. One for # and one for www. Once the www record was added to DNS, verification worked for both www.mydomain.ninja and mydomain.ninja. Odd, but maybe this will help someone else.