{"id":79640,"date":"2021-12-15T11:30:19","date_gmt":"2021-12-15T17:00:19","guid":{"rendered":"https:\/\/www.whizlabs.com\/blog\/?p=79640"},"modified":"2021-12-20T06:18:51","modified_gmt":"2021-12-20T11:48:51","slug":"cloud-dns-a-complete-guide","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/","title":{"rendered":"Cloud DNS &#8211; A Complete Guide"},"content":{"rendered":"<p><b>Google Cloud DNS<\/b><span style=\"font-weight: 400;\"> is better known as Domain Name System service. It has a job to publish the domain names to the global platform or DNS with a cost-effective approach. Cloud DNS helps organizations and IT developers to publish the zones within DNS without the efforts of managing their own software and DNS servers.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Cloud DNS has the potential to do that for them! Google Cloud DNS offers public as well as privately managed zones under DNS. The public zone is set to be visible over the public internet, but the private zone is considered to be visible only from the specified VPC networks.<\/span><\/p>\n<blockquote><p>Interested in Google Cloud Certifications? Whizlab provides high class online courses, practice tests and free tests. Check them out<a href=\"https:\/\/www.whizlabs.com\/google-cloud-certifications\/\" target=\"_blank\" rel=\"noopener\"><strong> here<\/strong><\/a>!<\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">With the implementation of shared VPC, Cloud DNS-managed zones, such as private zone, DNS forwarding zone, and DNS peering zone, will be created within the host project. In case of the private zones,<a href=\"https:\/\/www.whizlabs.com\/blog\/google-cloud-platform\/\" target=\"_blank\" rel=\"noopener\"> Google Cloud<\/a> takes the load of providing inbound &amp; outbound DNS. Apart from all of it, <\/span><b>Cloud DNS<\/b><span style=\"font-weight: 400;\"> is also offering DNS server policies and forwarding zones to permit the lookup sessions for special DNS names between the Google Cloud environment and on-premises cloud environment.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Cloud DNS intends to offer you service proficiency! Therefore, if you intend to learn more about this service by Google, you should put your efforts into finishing off this article! In this article, you will intend to get clarity upon how Cloud DNS service does its part in helping businesses and organizations thrive.<\/span><\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_76 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #ea7e02;color:#ea7e02\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #ea7e02;color:#ea7e02\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Working_Overview_of_Cloud_DNS\" >Working Overview of Cloud DNS<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Pricing_for_Cloud_DNS\" >Pricing for Cloud DNS<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#_1_Query_Pricing\" >\u00a0 \u00a01. Query Pricing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#_2_Zone_Pricing_Managed\" >\u00a0 \u00a02. Zone Pricing (Managed)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Server_Types_and_Routing_Methods_within_Cloud_DNS\" >Server Types and Routing Methods within Cloud DNS<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#1_Authoritative_Server\" >1. Authoritative Server<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#2_Recursive_Resolver\" >2. Recursive Resolver<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Supported_DNS_record_types\" >Supported DNS record types<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#1_Type_1\" >1. Type 1<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#2_Type_2\" >2. Type 2<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#3_Type_3\" >3. Type 3<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Process_of_Setting_up_Domain_with_the_use_of_Google_Cloud_DNS\" >Process of Setting up Domain with the use of Google Cloud DNS<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Step_1_Register_the_Domain\" >Step 1: Register the Domain\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Step_2_Creating_VM_Instance\" >Step 2: Creating VM Instance<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Step_3_Setting_up_Domain_with_Cloud_DNS\" >Step 3: Setting up Domain with Cloud DNS<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Final_Verdict\" >Final Verdict<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/www.whizlabs.com\/blog\/cloud-dns-a-complete-guide\/#Assess_your_understanding_of_Cloud_DNS-_Click_Here\" >Assess your understanding of Cloud DNS- Click Here<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Working_Overview_of_Cloud_DNS\"><\/span><b>Working Overview of Cloud DNS<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Domain Name System (DNS) is termed to be a distributed database that operates upon a specified hierarchy. It allows you to store IP addresses over its server, along with all of the other important data. Along with that, DNS also allows you to look and assess that data by searching it as per the names that you used to store it. Google Cloud has stacked up inbound &amp; outbound DNS forwarding methods for the private zones. You have the potential to configure the DNS forwarding aspects by creating a respective zone or a DNS server policy.<\/span><\/p>\n<blockquote><p><a href=\"https:\/\/www.whizlabs.com\/blog\/google-cloud-platform\/\" target=\"_blank\" rel=\"noopener\"><strong>Click Here<\/strong><\/a> to read more about Introduction to Google Cloud Platform!<\/p><\/blockquote>\n<p><span style=\"font-weight: 400;\">Under the inbound forwarding method for the private zones, you are demanded to create a server policy, especially for inbound implementation. It is to enable the on-premises server or client for DNS to send the requests to Google Cloud DNS. As a result, the DNS server or client will be able to resolve the records as per the name-resolution order of the VPC network. The clients over the on-premises DNS servers have the potential to resolve records within forwarding, peering, and private zones. The VPC network is authorized for the same!<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For outbound DNS forwarding methods, you are allowed to configure the VMs in a specific VPC network for different service aspects. You can configure the virtual machines for sending DNS requests to the specific DNS servers, as per your choice. You will be able to locate the name servers within the same VPC network. When you locate the same, it can be either over the internet or any on-premise network. Not just that, but the VMs you create can help you resolve the records that are being hosted over the name servers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">All of the resolved records are under the configuration of forwarding targets of a specific forwarding zone. It has the authorization for use by the specified VPC network. If you intend to learn more about the forwarding targets and the routing methods, then you can refer to this\u00a0<\/span><a href=\"https:\/\/cloud.google.com\/dns\/docs\/overview#fz-targets\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">official documentation by Google<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With Cloud DNS, you have the liberty to put up the configuration of inbound &amp; outbound DNS forwarding for the VPC network. There is a bi-directional forwarding potential that allows the Virtual Machines (VMs) within the VPC network, resolves the records upon the on-premise network or other networks that are hosted or carried out by diverse cloud providers. Hence, this kind of forwarding method gives potential to the hosts over the on-premise network to resolve the records for all of your resources within <a href=\"https:\/\/www.whizlabs.com\/google-cloud-certifications\/\" target=\"_blank\" rel=\"noopener\">Google Cloud<\/a>.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The control plane of <\/span><b>Cloud DNS<\/b><span style=\"font-weight: 400;\"> makes use of an algorithm for determining the responsiveness of any forwarding target. The outbound queries that are forwarded might experience certain server failure errors during their execution. There is a specific approach towards rectifying and managing it. Check out this documentation to understand more about server failure or\u00a0<\/span><a href=\"https:\/\/cloud.google.com\/dns\/docs\/troubleshooting#outbound-forwarded-queries-receive-servfail-errors\" target=\"_blank\" rel=\"noopener\"><i><span style=\"font-weight: 400;\">SERVFAIL errors upon outbound forward queries<\/span><\/i><\/a><span style=\"font-weight: 400;\">.\u00a0\u00a0<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Pricing_for_Cloud_DNS\"><\/span><b>Pricing for Cloud DNS<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The pricing associated with Cloud DNS is based upon per zone per month aspects. It doesn\u2019t matter whether you are using your zone or not, but you have to pay for it every month. Apart from that, you are also liable to pay for the queries that are present within your zone.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The pricing is uniform for all the zones, public, forwarding, or private. It means that if you have 10 zones of each, then your overall billing will be upon 30 zones uniformly. All of the queries are also aggregates, without concern upon the zone type. The pricing list for <\/span><b>Cloud DNS<\/b><span style=\"font-weight: 400;\"> is as follows:<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"_1_Query_Pricing\"><\/span><b>\u00a0 \u00a01. Query Pricing<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>&nbsp;<\/p>\n<ul>\n<li aria-level=\"1\"><span style=\"font-weight: 400;\">For the number of queries, ranging between 0 to 1 billion, you will have to pay $0.40 per million queries\/month.<\/span><\/li>\n<li aria-level=\"1\">When the number of queries crosses the 1 billion mark, then you will have to pay $0.20 per million queries\/month.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"_2_Zone_Pricing_Managed\"><\/span><b>\u00a0 \u00a02. Zone Pricing (Managed)<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><b><\/b>If you have a total of 0 to 25 zones, then you will have to pay $0.20 per managed zone\/month.<\/li>\n<li><span style=\"font-weight: 400;\">If you have a total of 26 to 10,000 zones, then you will have to pay $0.10 per managed zone\/month.<\/span><\/li>\n<li><span style=\"font-weight: 400;\">If you have a total of over 10,000 zones, then you will have to pay $0.03 per managed zone\/month.<\/span><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Server_Types_and_Routing_Methods_within_Cloud_DNS\"><\/span><b>Server Types and Routing Methods within Cloud DNS<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">The DNS server policies have the potential to specify inbound and outbound DNS forwarding. Not just that, but by specifying the server policies in an ideal manner, you can specify both of these forwarding methods at once. A DNS server takes the mantle of storing the database of the domain names and then processes them, as per the DNS queries, that come from any of the clients within a network.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">There are two types of servers available over Google Cloud DNS, that includes Authoritative server and Recursive resolver. Here is a brief description for both of them:<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"1_Authoritative_Server\"><\/span><b>1. Authoritative Server<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Authoritative server takes the responsibility of holding the DNS name records, which involves CNAME, A, AAAA. Any of the DNS servers that are non-authoritative tends to construct cache files, with resemblance to the past queries for domains. There is no option for holding out original name records.\u00a0<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Recursive_Resolver\"><\/span><b>2. Recursive Resolver<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">It is the DNS server that sends out queries to both authoritative &amp; non-authoritative servers for resolution. The name of this server intends that it has the potential of performing each of the queries for the name provided and returns the final output.\u00a0<\/span><\/p>\n<h2 id=\"records\"><span class=\"ez-toc-section\" id=\"Supported_DNS_record_types\"><\/span><b>Supported DNS record types<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Cloud DNS supports the following types of records<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Record type<\/b><\/td>\n<td><b>Description<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">A<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Address record, which maps host names to their IPv4 address.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">AAAA<\/span><\/td>\n<td><span style=\"font-weight: 400;\">IPv6 address record, which maps host names to their IPv6 address.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">CAA<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Certificate Authority (CA) Authorization, which specifies which CAs are allowed to create certificates for a domain.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">CNAME<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Canonical name record, which specifies alias names.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">DNSKEY<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The DNSSEC key from another operator for secure transfer. This record set type can only be added to a DNSSEC-enabled zone in Transfer state.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">DS<\/span><\/td>\n<td><span style=\"font-weight: 400;\">The DNSSEC key fingerprint for secure delegated zone. This record set type does not activate DNSSEC for a delegated zone unless you enable (and activate) DNSSEC for this zone.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">IPSECKEY<\/span><\/td>\n<td><span style=\"font-weight: 400;\">IPsec tunnel gateway data and public keys for IPsec-capable clients to enable opportunistic encryption.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">MX<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Mail exchange record, which routes requests to mail servers.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">NAPTR<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Naming authority pointer record, defined by RFC 3403<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">NS<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Name server record, which delegates a DNS zone to an authoritative server.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">PTR<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Pointer record, which is often used for reverse DNS lookups.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">SOA<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Start of authority record, which specifies authoritative information about a DNS zone. An <\/span><span style=\"font-weight: 400;\">SOA<\/span><span style=\"font-weight: 400;\"> resource record is created for you when you create your managed zone. You can modify the record as needed (for example, you can change the serial number to an arbitrary number to support date-based versioning).<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">SPF<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Sender Policy Framework record, a deprecated record type formerly used in email validation systems (use a TXT record instead).<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">SRV<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Service locator record, which is used by some voice over IP (VoIP), instant messaging protocols, and other applications.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">SSHFP<\/span><\/td>\n<td><span style=\"font-weight: 400;\">SSH fingerprint for SSH clients to validate the public keys of SSH servers.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">TLSA<\/span><\/td>\n<td><span style=\"font-weight: 400;\">TLS authentication record for TLS clients to validate X.509 server certificates.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">TXT<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Text record, which can contain arbitrary text and can also be used to define machine-readable data, such as security or abuse prevention information.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A TXT record can contain one or more text strings; the maximum length of each individual string is 255 characters<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">When you intend to add the forwarding targets to the forwarding zones, then you are demanded to choose between two available routing methods. The two methods include Standard Routing and Private Routing. Standard routing has the potential of routing the traffic through the authorized VPC network or through the internet, depending upon the IP address of the forwarding target. It should be RFC 1918 IP address! But in the case of private routing, the traffic is always routed through the authorized VPC network, without depending upon the IP address of forwarding target.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">There are basically three types of forwarding targets that are named as Type 1, Type 2, and Type 3. They are different from one another in terms of their standard and private routing supports. Here is a brief elaboration upon all of these forwarding target types.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"1_Type_1\"><\/span><b>1. Type 1<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">It is an internal IP address of the Google Cloud Virtual Machine within the same VPC network. It is authorized especially to make use of the forwarding zone.\u00a0<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Type_2\"><\/span><b>2. Type 2<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">It is an IP address over the on-premises system that is connected seamlessly to the VPC network. It has the authorization to query the associated forwarding zone using Cloud Interconnect and Cloud VPN.\u00a0<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Type_3\"><\/span><b>3. Type 3<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><span style=\"font-weight: 400;\">It is an external IP address of the DNS server that is accessible to the internet or external IP of Google Cloud resource. For instance, this type can allow access to external IP of VM in some other VPC network.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For accessing the Type 1 or Type 2 forwarding target, <\/span><b>Cloud DNS<\/b><span style=\"font-weight: 400;\"> intends to adapt routing within the authorized VPC network. There is no such compulsion to consider the IP address of the target. For sending traffic to the Type 1 forwarding targets, Cloud DNS makes use of\u00a0<\/span><a href=\"https:\/\/cloud.google.com\/vpc\/docs\/routes#subnet-routes\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">subnet routes<\/span><\/a><span style=\"font-weight: 400;\"> that are automatically created! For replying, these forwarding targets then make use of a specific return route for the Cloud DNS responses.\u00a0\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you intend to send traffic to Type 2 forwarding target, then Cloud DNS will use custom static routes or dynamic routes. But the custom static routes that come with network tags are not feasible to be used over Type 2 targets. Along with that, the Type 2 targets make use of routes within the on-premises network for replying. If you wish to learn more about the network requirements associated with Type 1 &amp; Type 2 targets, you can check upon this official documentation that highlights the\u00a0<\/span><a href=\"https:\/\/cloud.google.com\/dns\/docs\/zones#private_targets\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">network requirements<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Process_of_Setting_up_Domain_with_the_use_of_Google_Cloud_DNS\"><\/span><b>Process of Setting up Domain with the use of Google Cloud DNS<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400;\">As of now, you are well aware of how <\/span><b>Google Cloud DNS<\/b><span style=\"font-weight: 400;\"> helps streamline the accessibility of your data. Now is the time for you to learn the ideal steps to set up a domain to begin its implementation. The following process of setting up a domain is considering that you already have your Google Cloud account over the portal. The next steps are as follows:<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Register_the_Domain\"><\/span><b>Step 1: Register the Domain\u00a0<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ol>\n<li><span style=\"font-weight: 400;\">Head out to Google Domains by clicking on this <\/span><a href=\"https:\/\/domains.google.com\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">link<\/span><\/a><span style=\"font-weight: 400;\">. If you already have a domain, then you can head directly to Step 2 by skipping it.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Check for all of the names that are available to be picked as a domain.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Choose any available name as your domain.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Add it to the cart for buying it.<\/span><\/li>\n<li><span style=\"font-weight: 400;\">You need to set the auto-renewal and privacy settings before making the final purchase.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Complete the registration process, and then make the purchase.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">You can head to the \u2018My Domain\u2019 section to check out the domains that you own.<\/span><\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Creating_VM_Instance\"><\/span><b>Step 2: Creating VM Instance<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ol>\n<li><span style=\"font-weight: 400;\">Head to the \u2018VM Instances\u2019 page over the Google cloud portal.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Click on \u2018Create instance.\u2019<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Go to the \u2018Boot Disk\u2019 section. You will now have to click upon \u2018Change\u2019 to begin with configuration of the boot disk.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">When you reach for the \u2018Public Images\u2019 tab, you will have to choose \u2018Debian Version 9\u2019 over it.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Now, go ahead and click on select.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Head to the \u2018Firewall\u2019 section, and select the option that says, \u2018Allow HTTP Traffic.\u2019<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Now, click on \u2018Create\u2019 to complete the creation of the VM instance.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Head to the VM instances page, and click on \u2018SSH\u2019 on the instance that you created. It will let you connect to your instance.<\/span><\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Setting_up_Domain_with_Cloud_DNS\"><\/span><b>Step 3: Setting up Domain with Cloud DNS<\/b><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ol>\n<li><span style=\"font-weight: 400;\">Head to \u2018Create a DNS Zone page\u2019 over the <\/span><a href=\"https:\/\/console.cloud.google.com\/networking\/dns\/zones\/~new?_ga=2.17386876.498971288.1629073680-649812948.1628556136&amp;_gac=1.52052315.1628562381.CjwKCAjwpMOIBhBAEiwAy5M6YKCZ0qRlBu4PuyJGY1Ehe4-vzf37PUGdcqYg3rusd1hxy6ZIr_D9PRoCwG0QAvD_BwE\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">console<\/span><\/a><span style=\"font-weight: 400;\">.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Select \u2018Public\u2019 over the tab, Zone Type.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Enter zone name in the dedicated section.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Turn off the DNSSEC setting<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Now, click on \u2018Create\u2019 to create the DNS zone.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">For pointing the domain name to the IP address of hosting server, add A record to the zone.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Head to the zone details page, click on \u2018Add Record Set.\u2019<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Select \u2018A\u2019 for the \u2018Resource Record Type\u2019 menu.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Under the \u2018IPv4\u2019 section, give the external IP of your instance.<br \/>\n<\/span><\/li>\n<li><span style=\"font-weight: 400;\">Now, click on \u2018Create\u2019 to set the A record for your zone.<\/span><\/li>\n<\/ol>\n<h2><span class=\"ez-toc-section\" id=\"Final_Verdict\"><\/span><b>Final Verdict<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><b>Google Cloud DNS<\/b><span style=\"font-weight: 400;\"> has 100% availability and assures low latency. It supports automatic scaling to a large number of <\/span><a href=\"#records\">records<\/a> and zones. You have the reliability to create &amp; update millions of DNS records. The name servers over Cloud DNS scales on automatic measures to handle the complete query volume.<\/p>\n<p><b>Cloud DNS<\/b><span style=\"font-weight: 400;\"> makes use of the global network of anycast servers to serve the DNS zones. Hence, this is the potential that Google Cloud offers its users for streamlining their business and organizational approaches. Head out to get practical experience upon using Cloud DNS.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Assess_your_understanding_of_Cloud_DNS-_Click_Here\"><\/span><strong>Assess your understanding of Cloud DNS- <a href=\"https:\/\/docs.google.com\/forms\/d\/1807IVVz-EmbKh57wpiTdshgIPZstdMxjZvYaVQS0Wi0\/edit\" target=\"_blank\" rel=\"noopener\">Click Here<\/a><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><em>No Credit Card Required<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google Cloud DNS is better known as Domain Name System service. It has a job to publish the domain names to the global platform or DNS with a cost-effective approach. Cloud DNS helps organizations and IT developers to publish the zones within DNS without the efforts of managing their own software and DNS servers.\u00a0 Cloud DNS has the potential to do that for them! Google Cloud DNS offers public as well as privately managed zones under DNS. The public zone is set to be visible over the public internet, but the private zone is considered to be visible only from [&hellip;]<\/p>\n","protected":false},"author":169,"featured_media":79641,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[12],"tags":[4649,4654,4651,4655,4653,4652,4650],"class_list":["post-79640","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-google-cloud","tag-cloud-dns","tag-dns-record-types","tag-pricing-of-cloud-dns","tag-process-of-setting-up-domain-with-the-use-of-google-cloud-dns","tag-routing-methods-within-dns","tag-types-of-cloud-dns","tag-working-of-cloud-dns"],"uagb_featured_image_src":{"full":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",600,315,false],"thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide-150x150.png",150,150,true],"medium":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide-300x158.png",300,158,true],"medium_large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",600,315,false],"large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",600,315,false],"1536x1536":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",600,315,false],"2048x2048":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",600,315,false],"profile_24":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",24,13,false],"profile_48":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",48,25,false],"profile_96":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",96,50,false],"profile_150":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",150,79,false],"profile_300":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",300,158,false],"tptn_thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide-250x250.png",250,250,true],"web-stories-poster-portrait":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",600,315,false],"web-stories-publisher-logo":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",96,50,false],"web-stories-thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2021\/08\/Cloud-DNS-A-Complete-Guide.png",150,79,false]},"uagb_author_info":{"display_name":"Girdharee Saran","author_link":"https:\/\/www.whizlabs.com\/blog\/author\/girdharee\/"},"uagb_comment_info":10,"uagb_excerpt":"Google Cloud DNS is better known as Domain Name System service. It has a job to publish the domain names to the global platform or DNS with a cost-effective approach. Cloud DNS helps organizations and IT developers to publish the zones within DNS without the efforts of managing their own software and DNS servers.\u00a0 Cloud&hellip;","_links":{"self":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/79640","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/users\/169"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/comments?post=79640"}],"version-history":[{"count":8,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/79640\/revisions"}],"predecessor-version":[{"id":80503,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/79640\/revisions\/80503"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media\/79641"}],"wp:attachment":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media?parent=79640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/categories?post=79640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/tags?post=79640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}