Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Cakupan Cloud DNS adalah cara fleksibel untuk melampirkan resource DNS pribadi
ke objek Google Cloud . Awalnya, Anda hanya dapat melampirkan resource DNS pribadi seperti zona DNS pribadi, kebijakan, dan zona peering ke jaringan Virtual Private Cloud (VPC). Dengan menggunakan cakupan DNS, Anda dapat
melampirkan resource tidak hanya ke beberapa Google Cloud jaringan, tetapi juga ke
pengelompokan yang lebih kecil, seperti cluster Google Kubernetes Engine (GKE). Sebagai gantinya,
Anda dapat melampirkan resource DNS pribadi ke cakupan, bukan ke jaringan.
Cakupan Cloud DNS memungkinkan Anda melampirkan resource DNS pribadi ke jaringan VPC dan cluster GKE.
Dalam batas cakupan tertentu, seperti di jaringan, Anda dapat membuat tampilan DNS kustom. Misalnya, beberapa cluster GKE dalam
satu jaringan dapat memiliki hierarki DNS cluster.local-nya sendiri.
Anda dapat membuat zona DNS cakupan VPC atau cakupan cluster GKE,
bergantung pada apakah Anda ingin nama DNS terlihat oleh seluruh jaringan VPC atau membatasinya ke cluster GKE:
VPC scope. Gunakan cakupan ini jika nama DNS harus
diselesaikan di seluruh jaringan VPC. Zona DNS cakupan VPC memungkinkan nama DNS tersedia secara global untuk seluruh jaringan VPC.
Cakupan cluster GKE. Cloud DNS memungkinkan Anda membuat cakupan untuk satu cluster GKE.
Kemudian, Anda dapat membuat satu atau beberapa zona terkelola pribadi untuk setiap cluster, seperti yang dapat Anda lakukan untuk jaringan. Kueri dari dalam
cluster tersebut terlebih dahulu memeriksa apakah kueri dapat dijawab oleh
resource yang dicakup untuk cluster GKE tertentu tersebut. Jika tidak, kueri akan kembali ke pencocokan normal, yang dimulai dengan memeriksa apakah kueri dapat dijawab oleh resource cakupan jaringan.
Hierarki cakupan
Resolusi DNS terjadi pada cakupan paling spesifik yang tersedia, dengan menaiki
hierarki saat zona tidak ditemukan dalam cakupan yang lebih rendah. Cluster adalah cakupan yang paling spesifik, dan Cloud DNS akan memeriksanya terlebih dahulu untuk menemukan kecocokan.
Cakupan juga memungkinkan zona terkelola dan
kebijakan respons terikat ke satu atau beberapa pemilih dalam cakupan yang sama (jika berlaku). Anda dapat mengonfigurasi jaringan
dan cakupan untuk diikat dengan cara berikut:
Di antara beberapa jaringan
Antara cluster GKE dan jaringan
Di antara beberapa jaringan dan beberapa cluster GKE
Setelah Anda mengikat zona terkelola atau kebijakan respons ke pemilih, kebijakan tersebut akan terlihat oleh klien dalam cakupan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eCloud DNS scopes enable the attachment of private DNS resources to multiple Google Cloud networks or specific groupings like GKE clusters, offering enhanced flexibility compared to the previous VPC network-only method.\u003c/p\u003e\n"],["\u003cp\u003eDNS scopes allow for custom DNS views within their boundaries, such as multiple GKE clusters in a single network having their own \u003ccode\u003ecluster.local\u003c/code\u003e DNS hierarchy.\u003c/p\u003e\n"],["\u003cp\u003eYou can establish either a VPC-scoped DNS zone for network-wide DNS resolution or a GKE cluster-scoped DNS zone to confine DNS name resolution to a single GKE cluster.\u003c/p\u003e\n"],["\u003cp\u003eDNS resolution follows a hierarchy, starting with the most specific scope (the GKE cluster) and progressively checking broader scopes if a zone is not found.\u003c/p\u003e\n"],["\u003cp\u003eScopes enable managed zones and response policies to be bound to selectors within the same scope, allowing for flexible configurations between multiple networks, GKE clusters, or a combination of both.\u003c/p\u003e\n"]]],[],null,["# Scopes and hierarchies\n\nCloud DNS scopes are a flexible way of attaching private DNS resources\nto Google Cloud objects. Originally, you could only attach private DNS\nresources such as private DNS zones, policies, and peering zones to\nVirtual Private Cloud (VPC) networks. By using DNS scopes, you can\nattach resources not only to multiple Google Cloud networks, but also to a\nsmaller grouping, such as a Google Kubernetes Engine (GKE) cluster. Instead\nof attaching private DNS resources to networks, you can attach private DNS\nresources to scopes.\n\nCloud DNS scopes let you attach a private DNS resource to a\nVPC network and a GKE cluster.\nWithin the boundaries of a particular scope, like in a network, you can create\na custom view of DNS. For example, multiple GKE clusters in a\nsingle network can have their own `cluster.local` DNS hierarchy.\n\nYou can create a VPC-scoped or a GKE cluster-scoped\nDNS zone depending on whether you want DNS names to be visible to the entire\nVPC network or limit them to a GKE cluster:\n\n- **VPC scope**. Use this scope when DNS names have to\n be resolved VPC network-wide. A VPC-scoped\n DNS zone lets DNS names be available globally to the entire\n VPC network.\n\n- **GKE cluster scope**. Cloud DNS lets you\n create a scope for a single GKE cluster.\n You can then create one or more private managed zones for each\n cluster, just like you can for networks. Queries from within that\n cluster first check to see if the query can be answered by a\n resource scoped to that specific GKE cluster. If not, queries\n fall back to normal matching, which starts by checking if the query can be\n answered by any network-scoped resources.\n\nScopes hierarchy\n----------------\n\nDNS resolution occurs at the most specific scope available, walking up the\nhierarchy when a zone is not found in a lower scope. The cluster is the most\nspecific scope, and Cloud DNS checks it first for a match.\n\nScopes also let [managed zones](/dns/docs/key-terms#dns-managed-zones) and\n[response policies](/dns/docs/key-terms#response-policy) bind to one or more\nselectors within the same scope (when applicable). You can configure a network\nand a scope to bind in the following ways:\n\n- Between multiple networks\n- Between a GKE cluster and a network\n- Between multiple networks and multiple GKE clusters\n\nAfter you bind a managed zone or response policy to a selector, it is visible to\nclients within the scope.\n\nTo learn how to configure a cluster-scoped Cloud DNS zone, see\n[Configure a GKE cluster scope](/dns/docs/zones/configure-scopes).\n\nWhat's next\n-----------\n\n- To find solutions for common issues that you might encounter when using Cloud DNS, see [Troubleshooting](/dns/docs/troubleshooting).\n- To learn more about Cloud DNS response policies, see [Manage response policies and rules](/dns/docs/zones/manage-response-policies).\n- To learn more about zones, see [Create, modify, and delete zones](/dns/docs/zones)."]]
