Skip to main content

GCP Dns Managed Zone

A Google Cloud DNS Managed Zone is a logical container for a public or private DNS namespace hosted inside Google Cloud. It holds the resource-record sets that define how DNS queries for the zone’s domain names are answered. Managed zones can be public (authoritative on the public internet) or private (visible only to the VPC networks that are authorised to use them).
Official documentation: https://cloud.google.com/dns/docs/zones

Terrafrom Mappings:

  • google_dns_managed_zone.name

Supported Methods​

  • GET: Get a gcp-dns-managed-zone by its "name"
  • LIST: List all gcp-dns-managed-zone
  • SEARCH

ip​

If the zone contains A or AAAA records that resolve to specific IP addresses, Overmind links the managed-zone resource to those IP objects. This allows you to trace from a DNS name defined in the zone directly to the underlying address.

gcp-compute-network​

Private managed zones must be associated with one or more GCP VPC networks. Overmind therefore links the zone to every gcp-compute-network that is authorised to query it, helping you understand which networks can resolve the zone’s records.

dns​

Every record set stored inside the managed zone is discovered as an individual dns item. The managed zone is linked to each of these record items to show the parent-child relationship between the zone and its records.

gcp-container-cluster​

GKE clusters may automatically create or reference Cloud DNS managed zones for service discovery (for example, when using Cloud DNS for in-cluster DNS or when creating Ingress resources with managed certificates). Overmind links the zone to the originating gcp-container-cluster so you can see which clusters depend on, or manage, the zone.