I don't understand how this works. I have a domain registered at domainhoster X and a VPS at hoster Y. Since a week I am using the follwing DNS settings at my domainhoster X:
A RECORD (pointing to my server IP)
NAMESERVERS from my domain hoster
Now I registered on Cloudflare and added my domain. They told me to delete the domainhosters name servers and use their instead. Okay.
But: Do I have to delete the A RECORDS on at my domainhoster X, too and use only the A records entries on cloudflare?
If you change the NAMESERVERS of your domain to Cloudflare, your domain will follows the A RECORD rules on Cloudflare.
So you can but you don't have to delete the A RECORDS on your domainhoster X.
Only the A RECORDS changes on your Cloudflare DNS settings will have effect.
Related
Take for example I have bought my domain example.com at Namecheap.
I than set a custom customer name server in Namecheap because I am using Cloudflare as my authoritative DNS as follows
alpha.ns.cloudflare.com
beta.ns.cloudflare.com
Now my plan is to have DNS high-availability to prevent any DNS outage and ensure the accessibly my web application. I am going use another set of name server from Godaddy namely
ns01.domaincontrol.com
ns02.domaincontrol.com
So can I add these 4 name server record from 2 DNS provider in Namecheap to achieve high-availability ?
alpha.ns.cloudflare.com
beta.ns.cloudflare.com
ns01.domaincontrol.com
ns02.domaincontrol.com
what I have tried is I added these records but in Godaddy it is still showing "This domain is registered elsewhere. To use these DNS records on your domain, set your domain to these nameservers at your registrar:" , only in Cloudflare is active.
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.
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.
I have a domain name (somename.com) registered at godaddy and i am using godaddy DNS Manager. But i am hosting my website with hostinger.com. So i have created a subdomain (sub.somename.com) on hostinger which by default points to same IP as a domain.
Now i have entry on godaddy DNS for my domain and subdomain name which points to hostinger server address where my website hosted. But when i access my subdomain (sub.somename.com) it goes to my somename.com. I have to refresh it to load sub domain page correctly.
Godaddy DNS Entry
domainname -- somename.com -> IP address of hostinger.com
subdomain -- sub.somename.com --> IP address of hostinger.com (same as above)
Hostinger DNS Entry
subdomain -- sub.somename.com --> IP address of hostinger.com(same as above)
Is above entries is correct ?
Should we need to have entry for domain and subdomain both on godaddy DNS ?
Do we need to have a entry for subdomain in hostinger.com also ?
In order to create a subdomain correctly you have to go through 2 steps:
1. Update your DNS records, so they accept your subdomain (sub.somename.com).
You should have these records for your setup:
A: # -> IP of hostinger.com (this is to connect the domain with hostinger)
A: sub -> IP of hostinger.com (only put the subdomain name)
CNAME: * -> somename.com (so that everything before somename.com goes to somename.com)
CNAME: *.sub -> sub.somename.com (so that everything before sub.somename.com goes to somename.com)
There are different types of DNS Records, the one's you mentioned are all A Records, you have to use CNAME Records as well.
2. Creating a virtual host (on the hosting provider)
The previous step was so that the Domain Name Servers know to which ip to point when the subdomain is used. From this side we have to point the subdomain address (sub.somename.com) to a specific folder that contains the different website. Most host providers, when you create a subdomain automatically create a new folder you can put your content at and point at it.
So to answer your questions.
No you have to change your DNS Records so they match the information above. Let me remind you that changes in the DNS Records might take a while to take effect (1-2 hours).
Your DNS entries should be at one place. Usually they are provided by the hosting provider (hostinger in this case), but since they are also provided by GoDaddy as well feel free to update them there.
There is no need to have a DNS entry in hostinger if you update them in GoDaddy.
P.S. Since I haven't used hostinger before, feel free to update me if you have more info, like if you're using CPanel.
If you intend to host a subdomain at an IP different than your main site, the records should look like this.
Main Site (mysite.com)
Type: A
Name(Host): #
Value(Points To): 192.168.1.1
Blog Site (blog.mysite.com)
Type: A
Name(Host): blog
Value(Points To): 192.168.1.2
As a reference, you only need an A record to host a subdomain. CNAME record is an alias. www records are usually CNAME records to the root domain as they are the same page.
Hope this helps!
I have about 300 domains using my company DNS ns1.x.com.br and ns1.x.com.br
I want to use CloudFlare with all those 300 domains but when I add a domain to CloudFlare they give me new DNS that I need to change in my domains.
So far I added 70 domains to CloudFlare and they gave me only 3 sets of primary and slave DNS.
So, can I point my ns1.x.com.br to the primary DNS provided by CloudFlare? And do the same with the slave?
After that I will create a ns3.x.com.br and point it to another CloudFlare DNS. Will it work?
CloudFlare works at the DNS level in this way:
You have to signup for CloudFlare and add the domain (make sure all of your DNS records are in your DNS zone file at CloudFlare).
You then change to our nameservers at the registrar.
Only our nameservers can be at the registrar.
"So, can I point my ns1.x.com.br to the primary DNS provided by CloudFlare? And do the same with the slave?
After that I will create a ns3.x.com.br and point it to another CloudFlare DNS. Will it work?"
These records should be in your CloudFlare DNS zone file for the site(s) on those nameservers. They can't be active at the registrar because only CloudFlare's nameservers can be there for our service to properly work.
Note: I'm not sure if you're providing commercial hosting for sites. If yes, you might want to look at becoming a CloudFlare Hosting Partner instead (you don't have to worry about changing nameservers).
Yes, you can. There is a possibility to add domain in the new name server first you need to know the domain secret of each domain(It's a 6 Digit pin maintained with your current DNS)Theft Protection pin also needed. Both are same in the ResellerClub.
If you are using ResellerClub means Its Really easy to change, Because it has a Bulk Domain Booking option. That have a option "add existing Domain" option.
If You have any other Problem. Or this not a exact answer you need, Then please chat with me. I will update the answer. Thank You...