I own a domain foo.com and I am happy with where its DNS is hosted. I do want to delegate to Google Cloud DNS only a new subdomain bar.foo.com.
Is this possible?
Could you point me to example code?
What I need to do to the DNS settings of the servers hosting foo.com.
You should just be able to create NS records in foo.com called bar and enter the nameservers (one per entry) they gave you. That's called a "zone cut" and anybody looking up, say, baz.bar.foo.com will be told by foo.com to check with Cloud DNS (the same way com told them to check with foo.com). When they ask Cloud DNS, they'll get the answer.
So -
Set up the zone bar.foo.com on Google Cloud DNS
Add NS records at foo.com listing the Cloud DNS nameservers given
... that's it! Try it out.
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 am little new to hosting and so I am confused for take step. My current situation is like below
I have one big wordpress site in site ground. Domain is from Godaddy and I am using CloudFlar. I want move this site on Google cloud Instance. So I have created Google cloud instance and have installed Cpanel/WHM. I have copied site on newly created cpanel account. Now My confusion is How I should change DNS for point my domain to Google cloud.
Domain on : Godaddy, Using CloudFlare : Yes, Current Hosting : Site
Ground, New Destination Hosting : Google Cloud, My Current Domain :
example.com
For More information I have setup host like host.example.com and NameServer as ns1.example.com and ns2.example.com on Google cloud. Let me know someone can help me for required step to change DNS so I can successfully move without downtime.
Thanks a lot.
You need to update the IP address for your domain in the DNS records which are hosted either with godaddy or with cloudflare. If you are not sure, do a dig NS yourdomain.com See which dns server's are coming. and accordingly make the change.
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 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
I did the following steps but my domain was not getting resolved:
I created a zone (file) in Google Cloud -> Networking -> Cloud DNS using the right DNS name for the domain.
I put these NS as shown in Registrar Setup into my domain registrar:
ns-cloud-c1.googledomains.com
ns-cloud-c2.googledomains.com
ns-cloud-c3.googledomains.com
ns-cloud-c4.googledomains.com
I waited hours until the NS changes kicked in and verified in whois.
My domain was getting resolved.
Did I miss any other steps? I could not figure out so that I abandoned the Google Cloud DNS and went with my registrar's DNS and it is working now.
Make sure everything is spelled correctly.
i had trouble the other day. getting the domain to resolve while using google cloud services dns.
after waiting for about 30 hours, i double checked my work and found out that i had misspelled my domain name when i set up the dns zone.
usually the google dns entries resolve pretty quickly, especially if the domain is purchased from domains.google.com
the trailing . at the end has not been necessary for me. infact, when using domains.google.com, the trailing dot is automatically removed when entered as the custom dns-server.
All the NS you have listed doesn't have trailing . towards the end, as in
ns-cloud-c1.googledomains.com.
Would you be able to try updating the NS with your Registrar?
Have you already add a record (A record) to map the external IP address to your domain?
Your domain should be already working if you have all the records that are needed (and properly copied the NS record to your domain provider). However, for some time, you may need to wait for the propagation to change. See this link: https://cloud.google.com/dns/docs/overview#propagation_of_changes
In Google Cloud Platform, Cloud DNS has two requirements and I think you forgot the "A" record.
Requirements:
domain name from your domain name registrar.
IP address to point the A record of your zone. A valid IP address can be a server you already have running with an IP address you can point to.
To create an "A" record check below link:
https://cloud.google.com/dns/docs/quickstart#create_a_new_record