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.
Related
I'm after having associated a custom domain for firebase hosting and firebase dynamic links, I was trying to setup a custom domain for authentificatio email templates. However verification for the authentification fail.
I'm using Namecheap for the DNS configuration.
Is it because the cname and # directive conflict one with each other ? I chose a subdomain for the authentification template mail:
Information is DNS servers is public information. Trying to answer what is wrong is very hard when you hide the information required.
Go to Google Domains Is your domain verified in Google Domains? If not complete that step first.
The CNAME resource records appear correct.
Most likely the last two TXT records are wrong. I am guessing that you are using something like app.example.com. The managed zone is example.com. The host is app. Your TXT records should only have *app without the managed zone example.com.
After you modify DNS server resource records be prepared to wait. Firebase will say up to 48 hours.
If my answer does not solve your problem you will either need to disclose your DNS server resource records or find someone that understands DNS to help you.
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 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.
My domain verification process is completed and i also update my domain's DNS records to point to Firebase using "CNAME records" method (updated before approx 96 hours) but my site was not "Go Live". In Firebase console Hosting menu that give me below message:
Your site will go live when your domain registrar propagates your updated records.
I have already deploy my site default index.html using "Firebase deploy" CLI command and it's already successfully uploaded on "mydomainname.firebaseapp.com"
My Question: why my custom domain is not redirect to Firebase hosting?
Note: I have set default GoDaddy DNS nameservers in my domain.
I had the same problem and here is how i resolved it :
I put three parameters in the DNS record :
CNAME with www
A with 1st IP
A with 2nd IP
and then i only add two nameservers i.e.: ns1 & ns2 out of the 4 default Nameservers provided by name.com
and now my website is live on firebase.
-extra info:
it was not going live when i was using the 4 default nameservers.
it was not working with only one CNAME or both CNAME, or only both A with IP
I even contacted support on name.com they answered it is essential to have NameServer.
If you're using GoDaddy
Just try changing your host name from 'customdomain.com' to '#'
That worked for me
I could never get the "recommended" CNAME record to work. I ended up just using the two IP's for the A record. It took about 5 minutes to propagate enough to get my site in a browser.
If you are customizing your url domian with Godaddy and Firebase, you need to do the following:
Remove your existing A record (domains from Godaddy has one A record by default).
Add the A records from the instructions found in your Firebase Console.
If you want to use www.yourdomain.com, you need to set up the subdomain in Godaddy Domain (Attached image).
Maybe this step is not necesary, but I also added CNAME found in my Firebase Console.
After this changes you need to wait a few hours. If you problem persists Firebase has an excellent support as #FrankvanPuffelen says above. They solved my problems fastly.
For me after adding those 3, that #Orkun Ozen and #SarkawtNoori mentioned:
CNAME with www
A with 1st IP
A with 2nd IP
(without touching the nameservers)
in the domain service site (in my case hostinger).
I added a new domain to Firebase and called it www.mydomain.com including to mydomain.com and it worked perfectly.... (though I had to wait for it to be secure).
I deleted the custom firebase hosting site and added it again, actually when I did that it automatically was set as "connected". I didn't need to set up verification records or wait for provisioning.
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.