Changing my shared hosting nameservers to cloudflare nameservers - dns

I have signed up with cloudflare and i am running a website on shared hosting. I changed the nameservers of my domain on the shared hosting. I was expecting the website to not be available since i changed the nameservers but that has not happened yet.
I plan on confirming my domain on mailgun and having business email with google g-suite which both require i update srv settings in my domain.
My question is, why is my website still not offline and will the g-suite and mailgun changes be now done on the domain control panel or from cloudflare?.

If you changed the records at your registrar to connect to cloudflare, and then provide the appropriate A (or combination of A and CNAME) records in cloudflare you will be able to connect properly to your shared hosting and manage DNS records like SRV directly at cloudflare.

Related

Programmatically Connect domains to servers

I want to create a simple web app. where user can have a form to add domain and directory name( that is already created on our server ). And it simply starts pointing the domain to that directory. What apis should I need for this? Hosting and domains can be bought from same brand, like GoDady.
Cloudflare has an API to add DNS records.
However, if you go this route, these are the prerequisites:
User's domain must already be activated in Cloudflare. At least partial-setup with Cloudflare's hosting partner (Siteground etc which have Cloudflare integrations built-in) or full-setup (the domain's authoritative nameserver points to Cloudflare).
User must trust you with their email address linked to their Cloudflare account and their Global API key.
Your web app can then make the API call to the endpoint and Cloudflare will create the appropriate DNS records to point to your server.

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

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

Domain registrar's DNS records vs web hosting DNS records

I bought a domain from Google Domains. I have an A record (on Google Domains DNS control panel) pointed to my server's IP. I had a www CNAME record pointed to mydomain.tld. To experiment with my hosting panel's DNS (I have VestaCP) I deleted the www record from Google Domains DNS panel. There was already a www A record on VestaCP DNS panel. I deleted that and added a www CNAME record pointing to mydomain.tld. And suddenly my www.mydomain.tld stopped resolving. I also tried adding a test A record but I couldn't ping `test.mydomain.tld'.
So, how does hosting panel's DNS work? Each time I add a new website (be it a sub domain or a new domain itself) VestaCP creates certain DNS records. Are these DNS records supposed to override the ones in domain registrar's DNS panel or vice versa? What are DNS records in VestaCP DNS are there for?
When you have your hosting and domain in one single server or with one provider, your domain DNS will be with your domain itself. You just need to point the A record to hosting IP. Your Nameservers will be the default.
If you have your domain with one hosting provider and domain with other then you need to change your domain Nameservers to hosting nameservers. Then your DNS will migrate to your hosting account. The changes you may do in your domain panel will not affect. You can change your DNS settings from your hosting account only.
Hope it helps.

Link a shared webhosting to an external domain

I'm confusing on something!
If I map a domain with 1&1 with a shedhosting with bluehost. Do this means that I can manage my domain from bluehost ?
in other words can I manage my domain with 1a1 (emails, subdomains...) from my bluehost without transferring it.
Thanks,
Of course you can. By the default, your domain nameservers will use registrar nameservers, in your case 1&1 service. Simply login to your 1&1 account, then change your domain nameservers to bluehost nameservers. You can find your hosting nameservers in your hosting cPanel (I assume that bluehost use cPanel). Or, if you find a trouble finding the nameservers, simply contact bluehost customer service.
After change the nameservers, then check it first to make sure the changes was take effect, use http://who.is service. Then go to your bluehost cPanel, you can manage domain name directly from there, add/remove subdomain, change dns record (A Record, CNAME, etc..) and also your mail will functioned (I assume that bluehost give you an email hosting service in your hosting package).
NOTE: You don't need to transfer your domain to bluehost, you can have your domain registrar different from your hosting provider. The only thing you need to do just pointing nameservers to your hosting nameservers.
REMEMBER: All your domain record in 1&1 account will not functioned, you need to move it to your bluehost cPanel. All A Record, CNAME, etc in your 1&1 panel must be re-written in your bluehost cPanel.
I use this method right now, and everything is ok!

Resources