DeprecationDeskforced-migration deadlines

Google Cloud

Cloud DNS stops answering ANY queries in full and widens CNAME chasing on January 5, 2027

47 days left — Jan 05, 2027

What stops working
From January 5, 2027 Cloud DNS no longer returns full responses to DNS queries of type ANY and returns a single matching record instead. The same day Cloud DNS starts following CNAME chains across public and private zones in full VPC resolution order, so names in private zones or response policies that overlap public CNAME targets can resolve to unexpected addresses or fail.
Who is affected
Teams running Cloud DNS zones, in particular those with scripts, health checkers or monitoring that issue ANY queries, and those with private zones or response policies that overlap public CNAME targets.
Official migration path
Change tools to query specific record types or list records through the API, and test resolution paths for every CNAME chain with dig or nslookup before the date.
What the official path does not cover
Google does not tell the customer which clients send ANY queries or which private names collide with public CNAME chains; every zone and resolver path has to be inventoried and tested by the customer.
Source
Cloud DNS release notes, entry of Oct 27, 2026 · announced 2026-10-27 · verified 2026-11-19

Need this done before Jan 05, 2027?

Fixed price, fixed scope, fixed date. From $2,500 for a single integration or workflow; you get the working replacement, the code, and a before/after check. Quote within one business day.

Get a fixed-price quote →

One short form (company, email, what runs on this, needed-by). Reply within one business day.

Not ready yet? Get an email when Google Cloud deadlines approach · Firms: get listed for Google Cloud work.

Spotted a wrong date? Report it — corrected with the source within one business day.

← All deadlines