awverify CNAME not being picked up - azure

I have setup a CNAME for my domain using the awverify.www.DOMAIN.com. I'm using CloudFlare as my DNS provider. It's been more than 48 hours and using some dig tools on the internet, I can request the awverify domain and get the right response, yet Azure management portal still says it's not a relevant domain.
Any tips/advice???
Cheers!

Do you have that record marked with our proxy (orange cloud) in your DNS settings? That record may need to go direct until they verify (grey cloud). Try changing the cloud to off of CloudFlare in the DNS settings for that record to see if it helps.

Related

Delegate Subdomain to Azure via CNAME

the company I’m working for provided me a subdomain. test.mycomp.com . I want to add it to my azure web app via custom domain.
The azure system recommends a CNAME delegation and provided me the information to enter web-zeudz-staging.azurewebsites.net in the dns management as CNAME.
After doing so and verifiying via DNS Lookup, Azure always gives me „Domain Ownership Error“. What can I do to make this work?
Is your DNS provider also a CDN provider, for example cloudflare? If so, turn off the CDN/proxy function so it's a DNS only record and try again.
If you don't have any control over the CDN function you can use txt record validation.
Create your TXT record awverify.subdomain.test.mycomp.com with value web-zeudz-staging.azurewebsites.net and validate again. It should succeed.
There's also a CNAME awverify method but you need CDN disabled for that too.
I find it strange that your company doesn't have the option to enable/disabled CDN for any given DNS entry though.

Cloudflare Setup with Azure WebApp

I have a domain name registered with GoDaddy, e.g., "mysite.com", and have followed the Azure instructions to map that domain's CNAME and A records to my Azure WebApp, i.e.,
I then updated GoDaddy's nameservers to point to cloudflare so cloudflare is now in charge of my DNS records, i.e.,
Within cloudflare I have SSL set to Full and the certificate appears to be active
and my DNS records in cloudflare pointing to my azurewebsites domain name, i.e.,
It has been over 36 hours since I updated the nameservers, but as you can see from cloudflares DNS records screenshot above (see Status), all traffic appears to be routing around cloudflare directly to Azure, i.e., I'm not hitting cloudflare. Putting domain mysite.azurewebsites.net in whatsmydns also shows everything pointing to Azure.
What have I missed in the setup to ensure all traffic routes through cloudflare?
Probably a little late but you need to click on that grey cloud icon in Cloudflares settings. The icon will then go orange and the traffic will be routed through Cloudflare.
CloudFlare appears to transparently replace all CNAME records to A, so this CNAME record is not visible for Azure. You have to change nameservers of your domain to its original ones (provided by GoDaddy in your case), add CNAME through GoDaddy DNS panel, wait for Azure to see it, approve domain in Azure, and only then migrate to CloudFlare.

Client cname pointing to my domain on cloudflare

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

Azure - SSL & Traffic Manager - Multiple regions

I'm expanding my Azure SSL web app across multiple regions, and thus need to setup a traffic manager.
My current configuration works, and is:
SSL cert: www.bloop.com
Web App: uk-bloop.azurewebsites.net (Custom domain assigned)
Registrar (Go Daddy):
CNAME awverify awverify.uk-bloop.azurewebsites.net
CNAME awverify.www awverify.uk-bloop.azurewebsites.net
I can visit https://www.bloop.com, and everything works fine.
I now wish to add a USA region app: usa-bloop.azurewebsites.net into the mix.
I have added a traffic manager, and assigned the two endpoints, and it all seems to be working correctly:
bloop.trafficmanager.net
-> usa-bloop.azurewebsites.net
-> uk-bloop.azurewebsites.net
And that all seems great - the problem, is how can I assign a custom domain (& SSL Cert) to usa-bloop.azurewebsites.net? I cannot verify it, as the CNAME points to the uk region, and I cannot add two CNAME records, with the same name. If I point the CNAME to the traffic manager DNS, will Azure 'pass on' the verification to both the individual applications?
i.e:
Registrar (Go Daddy):
CNAME awverify awverify.bloop.trafficmanager.net
CNAME awverify.www awverify.bloop.trafficmanager.net
Minimum stuff required:
(you don't even need the awverify if CNAME is good enough - awverify is just for A)
Traffic Manager Endpoints:
Make sure your DNS configuration looks something like this (using tm.snobu.org instead of www.bloop.com):
$ dig tm.snobu.org
tm.snobu.org. 3397 IN CNAME simpletm.trafficmanager.net.
simpletm.trafficmanager.net. 97 IN CNAME app-eastus.azurewebsites.net.
app-eastus.azurewebsites.net. 1086 IN CNAME waws-prod-blu-039.vip.azurewebsites.windows.net.
waws-prod-blu-039.vip.azurewebsites.windows.net. 54 IN CNAME waws-prod-blu-039.cloudapp.net.
waws-prod-blu-039.cloudapp.net. 14 IN A 23.96.103.159
Set (the same) custom domain for both Web Apps:
Upload the SSL cert (in my case for tm.snobu.org) and set bindings for both Web Apps.
That's it.
The request shown above is not made over HTTPS because i don't have a cert handy, but you get the point.
In my opinion, you could configure SSL for each of your Azure websites, and configure DNS CNAME to point to the Traffic Manager, not the original website. And then you could add endpoints to point to your Azure Websites in Traffic Manager. I would recommend you to read this blog that explained how to scale Azure Websites globally with Traffic Manager.

Azure custom domain name with NetworkSolutions DNS

I'm having trouble setting up my domain purchased from networksolutions.com to azurewebsites.net or cloudapp.net.
Here are some of the resources I'm using, so far with no success. The instructions are varied and I also suspect that network solutions does not allow for the correct settings.
Has any body set up successfully with network solutions?
Configure custom domain name
Custom DNS website
!!UPDATE!!
Thanks to the answer.. here are the CORRECT NetworkSolution DNS settings to get you plugged into azurewebsites.net
Azure settings...
You need to edit the DNS Zone file. Check this link and this link.
The exact steps to setup a Custom Domain is as follows
Go to DNS Zone file and add a CNAME for domains like www.example.com or mysite.example.com. Add a DNS Record ( C-Record ) - "www" : "mygreateazuresite.azurewebsites.net"
Then come to Azure portal, in the Custom Domain Option, put the complete URL [ www.example.com ]
The process to set up custom domain for both Azure Websites and Azure Cloud Services are very similar
I have Found a nice step by step tutorial (azure web app + network solutions), same steps but a bit more detailed (including a simple tool to check your domain settings):
http://loldemar.azurewebsites.net/custom-domain-name-in-azure-using-network-solutions/
Basic steps:
Go to azure web app, go to configure tab, and choose manage domains, from there copy the IP address that is bellow this message (Help for IP Address THE IP ADDRESS TO USE WHEN YOU CONFIGURE A RECORDS)
Go to network solutions (advanced DNS Settings) in your Add IPAddress on your IP Address A Records (#).
The go to cname records and add
awverify.yoursitenamehere.net 7200 awverify.yourazuresitename.azurewebsites.net.
awverify.www.yoursitenamehere.net 7200 awverify.yourazuresitename.azurewebsites.net.
www.yoursitenamehere.net 7200 yourazuresitename.azurewebsites.net.
Now go back to azure, click again manage domains, and add your domain names (yoursitename.net and www.yoursitename.net)

Resources