You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
October 27, 2026
Starting January 5, 2027, CNAME chasing behavior will change so that Cloud DNS follows CNAME chains between public and private zones. If your private zones or response policies have overlapping domain names with public CNAME targets, queries might resolve to unintended internal IP addresses or return resolution errors.
The following table outlines the current and updated behaviors.
| Source of CNAME answer | Current behavior (until January 5, 2027) | New behavior (starting January 5, 2027) |
|---|---|---|
| Cloud DNS public zone | Subsequent queries search only public DNS zones and internal DNS. Private zones, forwarding zones, and response policies are ignored. | Subsequent queries follow the complete VPC name resolution order: response policies, private zones, forwarding or peering zones, internal DNS, and public zones. |
| Cloud DNS private zone | Subsequent queries search only authorized private zones. Public DNS zones are ignored. | Subsequent queries follow the complete VPC name resolution order. If the target isn't found in authorized private zones, Cloud DNS queries public DNS zones. |
| Cloud DNS response policy zone | Cloud DNS systems don't perform queries for CNAME answers received from response policy local data rules. | Subsequent queries follow the complete VPC name resolution order. If the target isn't found in response policies or private zones, Cloud DNS queries public DNS zones. |
Review your CNAME chasing needs before January 5, 2027. Test your DNS query paths
using dig or nslookup to identify CNAME chasing scenarios.
- Look for private-to-public CNAME chasing scenarios: Look for CNAME answers
from response policies or private zones that don't match any response policy
or record in a private zone. Previously, these queries resulted in a
NXDOMAINanswer but after January 5, 2027, these scenarios might match a record in a public zone or continue to beNXDOMAINresponses. - Look for public-to-private CNAME chasing scenarios: Look for CNAME answers
from public zones that don't match any record in a public zone. Previously,
these CNAME chasing scenarios would have resulted in a
NXDOMAINresponse. After January 5, 2027, these scenarios might match a response policy or record in a private zone or continue to beNXDOMAINresponses if the private zone doesn't have the record. - For CNAME chasing scenarios under your control: As best practice, configure matching time-to-live (TTL) values for all records in the CNAME chain.
Starting January 5, 2027, Cloud DNS will disable full responses to DNS queries of
type ANY (QTYPE=ANY) in public authoritative zones.
Instead, a single resource record will return for ANY queries, chosen from the
existing resource record sets that match the query.
Standard traffic from web browsers, applications, and API traffic query specific record types directly and are therefore unaffected with no action required.
However, certain legacy scripts, automated health checkers, debugging commands
(for example, dig example.com ANY), or custom third-party monitoring systems
that explicitly query ANY records will receive the first available record
instead of a full zone inventory. You must complete the following configuration
updates before January 5, 2027:
- Identify legacy queries: Review internal tools, deployment scripts, or
third-party DNS monitoring configurations for commands or API calls that
request the
ANYrecord type. Cloud DNS logs in Cloud Logging can be helpful with this. - Transition to specific queries: Update the tools to query the specific,
individual record types they require (for example, querying for
A,AAAA,MX, orTXTrecords separately). - Retrieve full zone records: If you use
ANYqueries to retrieve all records in a zone, use the Cloud DNS REST API (resourceRecordSets.list), the gcloud CLI (gcloud dns record-sets list), or the Google Cloud Console instead.
Risks associated with not making these changes include the following:
- False monitoring alarms: Automated uptime or DNS monitoring tools checking
ANYresponses may misinterpret the new response as a system failure and trigger false alerts. - Broken automation pipelines: Internal deployment or CI/CD scripts that
rely on parsing a full zone dump with an
ANYquery will fail to retrieve the expected data payload and may crash. - Disrupted IT diagnostics: Network administrators running manual legacy troubleshooting commands will no longer see a quick summary of all domain records, which could delay active network incident diagnostics.
October 12, 2026
Outbound Endpoints for Cloud DNS is available in Preview.
Attach Outbound Endpoints to forwarding zones or server policies to enable direct DNS query forwarding from VPC networks to external and on-premises DNS resolvers using private IP addresses. For more information, see Outbound Endpoints overview.
March 15, 2026
The filter query parameter for resourceRecordSets.list is generally available (GA).
You can filter records to match a specified domain using the API.
January 16, 2026
Monitoring your internet-bound DNS queries for malicious activity using DNS Armor is generally available (GA).
For more information, see Advanced threat detection with DNS Armor.
September 30, 2025
Alias records are available in GA.
This custom record type provides CNAME-like functionality at the zone apex, mapping the apex domain name to a canonical target.
August 29, 2025
Monitoring your internet-bound DNS queries for malicious activity using advanced threat detection from DNS Armor is now available in Preview.
For more information, see Advanced threat detection overview.
August 26, 2025
DNS64 is available in GA.
DNS64 provides synthesized IPv6 addresses for IPv4 destinations. For more information, see the following:
June 30, 2025
Using a fully qualified domain name (FQDN) forwarding target is available for outbound DNS forwarding in GA.
April 28, 2025
Using a fully qualified domain name (FQDN) forwarding target is available for outbound DNS forwarding in Preview.
February 21, 2025
Health checks for external endpoints in Cloud DNS routing policies are now available in GA.
January 30, 2025
August 08, 2024
You can now select internal proxy Network Load Balancers as a health checked target for DNS routing policies in Preview. For more information, see DNS routing policies and health checks.
July 31, 2024
Health checks for external endpoints in Cloud DNS routing policies are now available in Preview.
August 14, 2023
You can now select a cross-region internal Application Load Balancer as a health checked target for DNS routing policies. For more information, see Manage DNS routing policies and health checks.
August 07, 2023
You can now select internal Application Load Balancers as a health checked target for DNS routing policies. For more information, see Manage DNS routing policies and health checks.
February 22, 2023
Health checks for internal load balancers and automatic failovers in Cloud DNS routing policies are now available in GA.
December 14, 2022
Zonal Cloud DNS zones are now available in GA.
You can create private DNS zones that are scoped only to a Google Cloud zone.
Configuring Cloud DNS scopes is now available in GA.
December 05, 2022
Cloud DNS per resource IAM permissions are available in GA.
August 18, 2022
Health checks for internal load balancers and automatic failovers in Cloud DNS routing policies are now available in Preview.
August 16, 2022
Alias records are available in Preview.
You can now manage an alias record, which maps an alias domain name to a canonical name at the zone apex, by using Cloud DNS.
June 13, 2022
Cloud DNS per resource IAM permissions are available in Preview.
You can now set up specific read, write, or administrator permissions for different managed zones under the same project.
February 22, 2022
Zonal Cloud DNS zones are now available in Preview.
You can create private DNS zones that are scoped only to a Google Cloud zone.
February 07, 2022
This release fixes an issue in which Audit Logs for PATCH operations on managed zones and DNS server policies were not being generated.
January 21, 2022
Managing routing policies in Cloud DNS is available in GA.
November 12, 2021
The type of the vmInstanceId field in Cloud DNS's Stackdriver Logs has been changed from a number to a string.
November 09, 2021
Cloud Logging for managed public zones in Cloud DNS is now available in GA.
November 03, 2021
Managing response policies and rules in Cloud DNS is available in GA.
August 19, 2021
Managing routing policies in Cloud DNS is available in preview.
May 20, 2021
Cloud DNS monitoring dashboard is available in GA.
May 12, 2021
Configuring Cloud DNS scopes is now available in Preview.
March 24, 2021
The API for updating ResourceRecordSets in Cloud DNS is now available in GA.
February 16, 2021
Managing response policies and rules in Cloud DNS is available in Preview.
January 11, 2021
The API for updating ResourceRecordSets in Cloud DNS is now available in Beta.
May 18, 2020
DNS forwarding to a non-RFC 1918 address is available in General Availability.
January 07, 2020
Cloud DNS peering is available in General Availability.
November 19, 2019
DNS forwarding to a non-RFC 1918 address is available in Beta.
October 08, 2019
Private DNS User Facing Query Logging and Monitoring is available in General Availability.
September 24, 2019
DNS Forwarding is available in General Availability.
April 05, 2019
DNS peering is available in Beta.
Private DNS logging and monitoring is available in Beta.
March 26, 2019
Private zones support is available in General Availability.
March 12, 2019
Shared VPC service projects now support Cloud DNS private zones by default.
December 11, 2018
DNS forwarding is available in Beta.
October 23, 2018
Private zones support is available in Beta.
May 02, 2018
DNSSEC for Cloud DNS is available in General Availability.
November 02, 2017
DNSSEC for Cloud DNS is available in Beta.
March 06, 2017
Private zones for Cloud DNS is available in Alpha.
May 28, 2016
DNSSEC for Cloud DNS is available in Beta.
April 13, 2015
Cloud DNS is available in General Availability.