Google Cloud DNS alternative
Google Cloud DNS Without the Cloud Console
Google Cloud DNS is cheap, global, and managed: $0.20 a month for each of your first 25 zones and $0.40 per million queries (October 2026), with DNSSEC and IAM roles to match. It is also an infrastructure service, so the edits, the backups, and the morning checks are all yours. Managed DNS is $15 a month per domain, and we make the changes, copy the zone first, and compare the live records every day.
With Cascadia you get
- Changes made within two business days
- The zone copied before each change
- Every record checked each morning
- Ninety days of daily history
- No cloud project to log into
- The zone stays yours
Cascadia vs Google Cloud DNS at a Glance
Three Questions That Decide It
Do Your Systems Run in Google Cloud?
Do You Need Private Zones or Routing Policies?
Who Would Make the Next Change?
Side by Side
| Google Cloud DNS | Cascadia | |
|---|---|---|
| Price | $0.20 a zone plus $0.40 per million queries (October 2026) | –$15 a month per domain |
| Who makes changes | –You, inside a Google Cloud project (October 2026) | Us, within two business days of asking |
| Copy before a change | ×Yours to export | Full zone copied first, restored in seconds |
| Daily drift check | ×Yours to build | Live records compared every morning |
| Change history | –Audit logging in the project | Ninety days of day by day record history |
| DNSSEC | Managed keys, DS record at registrar (October 2026) | –Coordinated with your registrar |
| Private zones | Served to your VPC networks (October 2026) | ×Not part of this service |
| Routing policies | $0.70 per million queries (October 2026) | ×Not part of this service |
Price
Who Makes Changes
Copy Before a Change
Daily Drift Check
Change History
DNSSEC
Private Zones
Routing Policies
What the Standard Plan Includes
Cloud DNS charges for zones and queries and leaves the operating to you. At $15 a month per domain, this is the operating.
- Your record changes handled by us, within two business days of your request
- The entire zone copied before we edit a single record
- A bad change undone in seconds by restoring that copy
- Each morning, the live records checked against what we last set
- Our team alerted whenever something moves outside our process
- A day by day history of every record, ninety days deep
- SPF, DKIM, and verification records handled by people who know your zone
- Nameserver and TTL settings checked and kept sensible
- Every change logged, summarized in your report, and reversible
- No fee per change, and no ticket allowance to count down
Where Cascadia Goes Further
Google's console shows you a zone. It does not tell you that someone changed it last Tuesday.
Edits Without a Project Login
Cloud DNS permissions sit at project level or on single zones, through roles such as DNS Administrator and DNS Reader. Here you ask by message and the record is in place within two business days.
A Copy Before, a Comparison After
Every change starts with a copy of the whole zone and ends with a check against what it was meant to do. If it goes wrong, the copy goes back in seconds.
DNSSEC Without the Three Part Dance
Google's DNSSEC guide says it must be set up in the zone, with a DS record at your registrar, and with validating resolvers. We guide the registrar side so the chain holds.
Fairness to Google
Anycast serving from many locations, private zones, routing policies, and inbound and outbound forwarding are real strengths. If you run workloads in Google Cloud, Cloud DNS belongs next to them.
Who This Comparison Is For
Small businesses with a zone in a forgotten project
An agency created the project for a launch years ago. The records answer, but the access belongs to someone who left.
Teams Who Pay Google Pennies and Spend Hours
Five zones and 10 million monthly queries come to about $5 a month in Google's own example (October 2026). The cost you feel is the time.
Companies That Need Email and Verification Records Right
SPF, DKIM, and domain verification records are easy to get slightly wrong in a bare console.
Choose Google Cloud DNS if
- Your workloads already run in Google Cloud
- You need private zones or routing policies
- Engineers on staff manage the project
Choose Cascadia if
- Your DNS sits in a project nobody opens
- You want changes made for you, not a console
- You want the records checked every morning
Moving Your Zone from Google Cloud DNS in Four Steps
Most of the work happens before anything is switched.
- 1
We Read the Managed Zone
Each record set, its target, and whether it is still in use. Anything relying on a routing policy is flagged, since it needs a plain equivalent first.
- 2
We Rebuild It and Check Every Record
The zone goes up on the platform we run, in an account in your name, and each record is compared with the Cloud DNS original before any nameserver moves.
- 3
The Nameservers Switch
Once the copy matches, nameservers are switched at your registrar. If DNSSEC is on, we guide the DS record at your registrar in the right order. Cloud DNS keeps answering for anyone holding the old ones.
- 4
The Old Zone Can Go
When you are satisfied, the managed zone can be deleted from the project. From then on, changes go through us.
How Google Cloud DNS Works
Cloud DNS Pricing and Features
Figures are from Google Cloud pages read in October 2026.
Taken from Cloud DNS pricing, Cloud DNS overview, Cloud DNS DNSSEC, Cloud DNS quotas. Checked October 2026.
What Clients Say About Working with Cascadia
“I’ve always dreaded website management, but Cascadia has done an incredible job with my WordPress site, making it one less thing for me to worry about.”
“I’ve worked with Cascadia for several years now. They are always ready to help in any way I ask and can implement my ideas with ease. A company that values their clients!”
“Cascadia has been great to work with! We recently needed some updates, and Cascadia was quick to get them completed! We highly recommend Cascadia Web Services.”
“Cascadia is very responsive and we’re happy with them as our primary IT vendor.”
“They do great work, been using for years. Prompt responses to requests.”
Ready to Move from Google Cloud DNS?
Talk to us about your setupAsk us
Google Cloud DNS Alternative Questions
What Cloud DNS costs, what it leaves to you, and how a move runs.
See Managed DNSStill have a question?
How much does Google Cloud DNS cost?
Managed zones are $0.20 a month for the first 25, with lower tiers after that. Queries are $0.40 per million up to 1 billion, then $0.20. Google's own example prices 5 zones and 10 million queries at $5.00 a month (October 2026).
Does Google charge for unused zones?
Yes. Zones are billed per month whether or not they receive queries, and the zone types are aggregated for pricing. A forgotten zone keeps costing a little each month (October 2026).
Is Cloud DNS cheaper than Managed DNS?
On the bill, yes. Five zones and ten million queries cost about $5 a month at Google, against $15 a month per domain here. You pay us for the edits, the copies, and the daily check, which Google does not offer (October 2026).
What does Cloud DNS include?
Public and private zones, managed DNSSEC, anycast serving from multiple locations, project or zone level IAM roles, DNS forwarding, and DNS Armor threat detection. It is an infrastructure service rather than a managed one (October 2026).
How does DNSSEC work on Cloud DNS?
Cloud DNS creates and rotates the keys and signs the data. You must also add a DS record at your registrar, and use validating resolvers. Without the DS record, turning it on in Cloud DNS has no effect (October 2026).
What happens to DNSSEC when we move?
Google says zones can migrate to or from other operators that support it without breaking the chain of trust. We guide the order of DS record changes at your registrar so validation does not fail during the switch.
What are routing policies, and can you replace them?
Routing policy queries cost $0.70 per million, and a policy can hold up to 100 items. We do not offer weighted or geographic routing. Any record that depends on one is flagged before the move (October 2026).
Can you manage our private zones?
No. Cloud DNS private zones serve only the VPC networks you specify, which is a cloud networking job. Our service covers public DNS for your domains (October 2026).
Who is allowed to edit a Cloud DNS zone?
Permissions are set at project level or per zone, using roles such as DNS Administrator and DNS Reader. Someone with the right role in the right project must sign in to make a change (October 2026).
Does Cloud DNS keep a copy of the zone before a change?
Not as a feature we could find on its overview. Changes are applied as additions and deletions, up to 1,000 of each per change. We copy the whole zone before each edit and keep Ninety days of daily history (October 2026).
What will you check each morning?
We compare the live records with what we last set. If an unexpected edit appears, our team is alerted, so a change by a registrar, plugin, or developer is caught before it becomes an outage.
How long does a record change take?
Changes are made within two business days of asking. There is no per change fee and no ticket allowance to count against.
Will there be downtime during the move?
No. We verify every record against the Cloud DNS original before nameservers move. Cloud DNS keeps answering for anyone still holding the old nameservers, so the switch is gradual.
Who owns the DNS account after the move?
Your company. The zone sits in an account in your name, and nobody at Cascadia holds it on your behalf. You can see every record in your portal at any time.
When should we stay on Cloud DNS?
When your workloads run in Google Cloud, you need private zones or routing policies, and engineers already manage the project. Cloud DNS fits that, and our fee would buy you little.
