Cloud DNS Peering Zone

Related topics

• Cloud DNS Peering Zone is part of Cloud DNS From the official documentation: “A peering zone is a type of Cloud DNS managed private zone that follows the name resolution order of another VPC network.”
• Cloud DNS Peering Zone works with forwarding zone From the official documentation: “You can then create peering zones for VPC networks B and C that point to the forwarding zone.”
• Cloud DNS Peering Zone works with managed zone From the official documentation: “Managed Zone is a global resource which creates Cloud DNS Peering Zone with the given target project.”
• Cloud DNS Peering Zone works with Shared VPC From the official documentation: “To use a Cloud DNS managed private zone, Cloud DNS forwarding zone, or Cloud DNS peering zone with Shared VPC, you must create the zone in the [host project](/vpc/docs/shared-vpc#concepts_and_terminology), and then add one or more Shared VPC networks to the list of authorized…”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• Cloud DNS works with GKE From the official documentation: “To create a new managed private zone using Cloud DNS for the GKE cluster, complete the following step.”
• forwarding zone is part of Cloud DNS From the official documentation: “You can use a forwarding zone in Cloud DNS to resolve queries for specific DNS names by sending them to another DNS server.”
• private zones is part of Cloud DNS From the official documentation: “Create a Cloud DNS private managed zone in any of your Google Cloud projects.”
• VPC Service Controls secures Cloud DNS From the official documentation: “You can use VPC Service Controls to secure your Cloud DNS configuration.”
• Cloud DNS works with managed zone From the official documentation: “Managed Zone is a global resource which creates Cloud DNS Peering Zone with the given target project.”
• GKE works with Shared VPC From the official documentation: “For networking, GKE clusters are deployed in a Shared VPC that's created as part of the enterprise foundation blueprint.”
• managed zone is part of Cloud DNS From the official documentation: “This page provides directions for creating, updating, listing, and deleting Cloud DNS managed zones.”
• private zones works with Shared VPC From the official documentation: “If you use Shared VPC networks within your organization, you must host all the private zones on Cloud DNS within the host project.”
• VPC Service Controls secures GKE From the official documentation: “The Kubernetes Engine API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”