I have a domain name myapp.com with GoDaddy, and I've deployed the site to Azure, so now the app is in myapp.cloudapp.net.
I'm trying to set up a CNAME from www.myapp.com to myapp.cloudapp.net but it doesn't work after two days and I was wondering if I've done something wrong.
I've set up a CNAME record from www to myapp.cloudapp.net in my DNS Manager in GoDaddy, and a forwarding from myapp.com to www.myapp.com. I did this on Friday.
When I try to access myapp.com I get redirected to www.myapp.com, but then it says "Page not found", actually if I do a ping, it cannot resolve www.myapp.com, but it can resolve myapp.com.
Of course, if I try myapp.cloudapp.net it works perfectly.
There is still an A record in the DNS Manager, should I remove it? What may I be doing wrong?
Cheers.
Before this is moved to SuperUser, do you have a hosting account with GoDaddy? The reason I ask is because they don't handle your DNS for you unless you pay for hosting too.
This leaves you with two options
Pay for it
Get it free
I recommend trying the free option first
Related
I have been figuring out how to accomplish this for a day now and read through a bunch of tutorials but could not make it work the way I wanted.
So my current set up is that I have a website that I registered the domain with Namecheap, let's call it mywebsite.com. The main app is hosted on Heroku, so both mywebsite.com and www.mywebsite.com is set up as URL redirect and CNAME to point to the heroku address. For example I have a CNAME record for www pointing to www.mywebsite.com.herokudns.com. This works fine and I would like to keep it that way.
I recently registered for a SiteGround service to set up my wordpress blog. I would like it to be accessible at blog.mywebsite.com. Most of the tutorial I have seen is to either migrate the domain to siteground so the wordpress site can point to the main domain or to point the namecheap DNS nameservers to the siteground one which I don't want to do neither because I do not want to redirect the traffic away from the heroku app.
I have tried to set up NSRecord according to Namecheap doc, I added the record for blog to point to ns1.siteground1111.com (the nameservers siteground provided) but when I entered blog.mywebsite.com it said server not found. I am on a SiteGround shared IP plan and I can see the blog if I visit ns1.siteground205.com/~myusername. However creating A record or CNAME requires bare IP and domain so I wonder if that's the issue.
My question is if my approach was correct in trying to set up the subdomain by creating a NSRecord on Namecheap pointing to SiteGround's nameservers. Or is it necessary for me to pay extra and get a dedicated IP address from SiteGround for me to point my A record for blog to.
Alternatively, I also have extra domains I am not using and I could set SiteGround blog to those domains and perhaps create a CNAME record for blog.mywebsite.com to www.myotherwebsite.com? That sounds like an overcomplication of the issue but I am not sure what to try at this point.
Really appreciate any help!
In Namecheap admin for your domain name mywebsite.com:
(1) Create an A record:
[type, host, value, TTL]
A, #, 1.2.3.4, 1min
where 1.2.3.4 is the Siteground IP address of your account.
(2) Create another A record:
A, blog, 1.2.3.4, Automatic
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
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.
I created an app on Openshift and added aliases.
My registrar doesn't allow me to add a CNAME without WWW. So I started using the Cloudflare DNS servers and added 2 CNAME records. In the records page it looks like this:
CNAME porta8080.com.br is an alias of blog-porta8080.rhcloud.com Automatic
CNAME www is an alias of blog-porta8080.rhcloud.com Automatic
I changed it like 3 or 4 ours ago and the domain status is already Active.
If I go to my website it won't be displayed if I omit the subdomain www. . But works well with www.
I wonder if I can do this with Cloudflare (with and without www.) and/or cloudflare is alrady routing for me. I got a free plan.
Thank you
#edit
Now I got a ERR_TOO_MANY_REDIRECTS error. Any ideas on what could this be?
CloudFlare Partner set-ups usually are done via a CNAME set-up. Unfortunately it doesn't strictly comply with an RFC to support a CNAME record on a root domain, accordingly you can either set-up your own CloudFlare account (you won't get RailGun if your host are not just a normal CloudFlare Partner but an Optimised Partner).
The way around this is either get them to support the Full Host set-up which CloudFlare now support or set-up your own CloudFlare account and use a nameserver install.
I'm not exactly sure if this is more of a DNS question or the nature of most PaaS's.
I purchased a domain from namecheap.com. I wanted to get a WordPress site up and running so I could start development so I went over to openshift, created an account and installed WordPress, which was very easy! Only one problem... I'm having issues trying to sync my domain name from namecheap with the application on openshift. I must admit I've always purchased the domain name and hosting together so I've never had to go this route so I'm not entirely sure this has anything to do with the fact openshift is a PaaS.
In openshift, I have the URL for my application applicationname-account.rhcloud.com and I've added an alias on my namecheap.com account which works for a redirect... If I go to my purchased domain, www.example.com, it will simply redirect me to example-account.rhcloud.com. But I do not want a redirect...
I guess I'm confused as to how you get a domain name that you've purchased from one company to a hosting company. Do I need to modify something on my namecheap account?
This document states that you need to add a bare CNAME record to your DNS setup (may be what you refer to as an alias)
https://www.openshift.com/blogs/custom-url-names-for-your-paas-applications-host-forwarding-and-cnames-the-openshift-way
then add an alias to your Openshift application using the rhc command line tool, eg:
rhc alias add example-account www.example.com