Cloud DNS Zones & Records
Public/private managed zones with record sets, DNSSEC, forwarding and peering configs.
Compare DNS & Traffic Management across clouds →
Part of: GCP Production Landing Zone
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o gcp-cloud-dns-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-cloud-dns/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-cloud-dns-1.0.0.sigstore.json \
gcp-cloud-dns-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "9d4d5179bcba3793b282e638ced0ca3ee4e9d6b2b6c7f590ce14e113e0c8d416 gcp-cloud-dns-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "cloud_dns" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-dns/gcp"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/gcp-cloud-dns?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Terraform module 1.0.0, live-tested on IaC Bazaar: [Cloud DNS Zones & Records](https://www.iac-bazaar.com/catalog/gcp-cloud-dns?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```hcl
module "cloud_dns" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-dns/gcp"
version = "1.0.0"
}
```Preview:
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
gcp-cloud-dns
A Cloud DNS managed zone with record sets — private by default
(resolvable only from the VPC networks you bind), with optional DNS
forwarding and peering for hybrid resolution, and DNSSEC signing
plus query logging turned on for public zones. Works with Terraform and
OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.
Secure defaults
- Private visibility by default — a zone is only resolvable from VPC networks (or GKE clusters) you explicitly bind. A plan-time precondition rejects a private zone with no network binding and no forwarding/peering, so you never ship a zone that resolves nowhere.
- DNSSEC on for public zones — signing enabled with NSEC3 authenticated denial of existence (the privacy-preserving mode that does not enumerate the zone).
- Query logging on for public zones — an audit trail of resolution.
force_destroy = false—destroywill not silently wipe a zone that still has records; you must opt in.- Forwarding vs peering are mutually exclusive, and forwarding/peering zones cannot also host record sets — both enforced as preconditions.
DNSSEC and query logging apply to public zones only and are ignored on private zones (which GCP cannot sign).
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/google>= 7.0, < 8.0
License
Commercial — LicenseRef-IaCBazaar-Commercial.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
- Inputs
- Outputs
Related modules
gcp-resolver-policy
A Cloud DNS server policy bound to no network resolves for nobody, and query logging is off by default, so nothing records which host resolved which name - the first question in most incidents. Refuses a policy with no networks, logs every query, and can add a response policy that answers listed domains with a sinkhole address before recursion, for every workload on every governed network at once.
civo-dns-zone
A Civo DNS zone with every record in one map, each with the TTL Civo requires per record, and the nameservers exported for the registrar. Civo does not sign zones and has no CAA or NS record types; dnssec_available says so, so a domain that needs DNSSEC is sent elsewhere before it is delegated.
do-dns-zone
A DigitalOcean domain and its records. Creating the zone does not delegate it: until the registrar's nameservers point here the zone is correct, complete and serving nobody, which looks exactly like a working zone. The domain's ip_address shortcut, which hides an apex A record from your records map, is deliberately not used, and a CNAME at the apex is refused.
tencent-dns-zone
A Tencent Cloud DNSPod zone with every record in one map, all on the default resolution line so every resolver gets the same answer, MX priority carried on the record, and the free-grade nameservers exported for the registrar. DNSSEC is not a resource in the provider; dnssec_available says so.
huawei-dns-zone
A Huawei Cloud public DNS zone with the flat record map grouped into the record sets Huawei expects (one per name and type, several values), DNSSEC on with the DS record for the registrar, and the nameservers exported. Private zones bound to a VPC are a different zone type and not this module.
azure-dns-private-resolver
A resolver is five resources - endpoints, ruleset, rules and VNet links - and the half-built state most sit in resolves Azure names and forwards nothing to on-premises; a ruleset not linked to a VNet applies to nothing; and each endpoint needs its own delegated subnet. All five created, forwarding rules required, VNet links expected (none by name), the inbound address exported.