What is Reddit's opinion of
Google Cloud DNS?
From 3.5 billion Reddit comments
12 reviews of this app found across Reddit:
I bought a small home server a few years back (10watt Intel Atom box with 1GB ram), and it's awesome. Steep learning curves, very frustrating at times, but very educational.
At first I only used it as a webserver, because I wanted to improve my webdesign/coding skills, and many webhosts were too restrictive to my taste. I wanted to try different languages/backends, experiment with SSL certificates, understand SQL better, etc.
But now my girlfriend uses it to host Mumble & Teamspeak as well. We use it for sharing documents and creating computer backups. I moved a few TB harddisks from my PC to the server so we can watch our movies/series from every room, or through owncloud streaming. I use it to host gaming servers, although that's a bit too demanding for the poor little machine sometimes.
And now I've hooked up most of the house as well: We were doing some home improvement, so all the lightswitches/dimmers/ventilation/thermostats/sensors/relays/etc are all routed through microcontrollers and connected to the server. Which, in turn, pushes notifications to our phones when the cat has pooped (volatile organic compounds sensor), when the shower goes over its daily water/kWh limit (flowmeters & smartmeters), or when the cooking stove is still on (IR thermometer, CO & Methane sensors).
So... a home server is a good way to get sucked into all kinds of useless fun projects :P
> I would have to find a free way around dynamic IPs though and I heard of problems with connections with IPV6 adresses.
DuckDNS, free and simple.
FreeDNS, free, also works with IPv6-only servers.
Google Cloud DNS, paid, but only about $0.20/m for a home server, reliable & very advanced.
What I finally did was set up Cloud DNS with Google. The only thing at the registrar, dotgov.gov, is a pointer to the name server. Once I set up the managed public zone then I updated the pointer to the name server at dotgov.gov. Here is a link to setting up the managed zone with Google. https://cloud.google.com/dns/docs/zones
It’s really very straightforward when you find the right resources.
If you're creating the DNS zone on Google Cloud DNS, it should be as easy as setting the zone to the "Transfer" DNSSEC status on GCP. That will generate DNSKEY records in the zone. These are the keys that should be submitted to the registrar. Once everything has propagated from the registrar and you confirm that you can see the keys being sent from the TLD nameservers, you can change the DNSSEC status in GCP from "Transfer" to "On".
If you want to use your own keys, just follow GCP's documentation
Edit: To answer your other question, once the keys are added to the zone, the GCP nameservers will do all the signing automatically, no need to manually sign each record.
You can change the name servers for the wix nameservers as /u/lolklolk said, or you can add all the records for your domain
I never used google as a dns provider but there is documentation about how to do it
- beacons.gcp.gvt2.com
- beacons.gvt2.com
are blocked (beacons3.gvt2.com btw isn't) and they're used for Google DNS services: https://www.whois.com/whois/gvt2.com
like
ns1.google.com
ns2.google.com
ns3.google.com
ns4.google.com
see https://cloud.google.com/dns/docs/dns-overview
so, i don't think any gvt2.com domain should be blocked.
I mean, my domain point to Google Could DNS:
NS 21600
ns-cloud-c1.googledomains.com.
ns-cloud-c2.googledomains.com.
ns-cloud-c3.googledomains.com.
ns-cloud-c4.googledomains.com.
Not sure about the terms though, but I think we're talking about the same thing, right? https://cloud.google.com/dns
You'll pay for queries against your domain anyway, right? (https://cloud.google.com/dns/pricing)
It sounds like you should just enable the Cloud DNS API. If you're concerned about paying a lot of money, I have a few Route 53 domains (AWS Route 53 is what Google Cloud DNS is competing with) and the domain monthly cost and all my queries run me about $3/mo.
you are right that no one gurrentee 100% dns uptime.
but
100% SLA => 100% dns uptime SLA. Soory for this mistake but
if it does not meet SLA then they will credit amount to future monthly bills of Customer.
the amount depends on the downtime slab rate. check this out.
https://cloud.google.com/dns/sla
also check this
The limit is at a minimum, what your DNS service (AWS Route53, Google Cloud DNS, Cloudflare) can handle. IE no limit
The 3 above are the "big players" so to speak but there are countless others. AWS for example has a published limit of 10,000 per hosted zone but I know this can be increased if you pay enough. Most other providers can also handle this limit or more.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html https://cloud.google.com/dns/quotas https://support.cloudflare.com/hc/en-us/articles/360017421192-Cloudflare-DNS-FAQ#CloudflareDNSFAQ-HowmanyDNSrecordscanIhaveperdomain
I recommend definitely keeping Cloudflare and from your CF account you can point DNS to your host. If you use CF then the nameservers should be pointed to CF, and then individual dns records set up in your CloudFlare account pointing to Google. Looks like they have documentation on how to:
https://support.cloudflare.com/hc/en-us/articles/360019093151-Managing-DNS-records-in-Cloudflare
Basically, all you have to do is to to create an A record and point it to your Google Cloud IP address. You should also make sure that the domain is using Google's authoritative DNS servers.
Please note that it may take up to 48 hours for the DNS changes to propagate across the Internet.
Whatever solution you end up moving to for your DNS service, here are the steps I would suggest:
Put a freeze on any changes to IP/Name assignments until your conversion to the new provider is complete + a couple of days.
Have your current DNS service provider extend the TTLs on the the records to give you time to recreate the zone on other solutions with minimal impact or failed queries. Hopefully frequent users of your domain sites and services will have a cached response. This step may not be required on non Network Solutions DNS providers. I know that on Network Solutions in the past, I could not create the zones until after I changed the registration to point to Network Solutions DNS.
Build your zone on the new DNS provider. This is made easier if you can do a full zone transfer or can at least get a zone dump file out of the current host.
Change your DNS host settings in the domain's registration.
Confirm that the new DNS zone is providing answers when queried directly.
Use any available reporting to monitor query count to make sure traffic is going to the correct DNS service. Perform tests from various network locations (ie. Cable provider, business location, mobile, etc.) to confirm the new service is providing the name information.
Now some additional advice - have you looked into potentially using Google Cloud DNS? They are significantly cheaper than DynDNS or UltraDNS (Neustar). My old company was using UltraDNS, and for the same number of queries and features, what would cost $700 a month with Ultra was under $50 with Google. You can find their pricing guide here: https://cloud.google.com/dns/pricing