PuppyIP Resource Center
Network And Account Troubleshooting 5 min Published 2026-11-20

Google Cloud DNS CNAME differs inside a VPC? Check the January 5 resolution change

Cloud DNS changes CNAME resolution on January 5, 2027. Later lookups for a public alias can match a VPC response policy or private zone. Collect a baseline from the affected workload and compare it after the change.

Google Cloud DNS CNAME VPC Private DNS

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • From January 5, 2027, Cloud DNS will evaluate VPC name resolution order independently at each CNAME hop.
  • A target can match a private zone and return an internal address. If the most specific matching private zone lacks the target record, the query can return NXDOMAIN.
  • Capture the chain, response code, and TTL from the actual workload and repeat the same query after the change. Compare publicly intended names using an approved public resolver.

Identify the resolver the workload actually uses

Google announced the change to subsequent CNAME lookups on October 27, 2026, with a planned start date of January 5, 2027. This guide uses a Compute Engine VM with the metadata server at <code>169.254.169.254</code> as its resolver and no alternative name server configured in the VPC outbound policy.

For applications in GKE or workloads that use custom DNS, an alternative name server, or forwarding, first confirm where the query originates and which service performs recursion. A direct query from a VM to its metadata resolver shows that resolver's result. Verify the application's result from its own runtime as well.

Check each target for an overlapping response policy or private zone

A CNAME points to another name. Under the announced change, the target of a CNAME obtained from a public zone can match VPC response policies, private zones, forwarding or peering zones, internal DNS, or public DNS. Subsequent targets from local private-zone or response-policy records can also follow the full order. Policy and zone bindings may differ between VPCs.

For example, suppose the public alias <code>app.example.com</code> points to <code>origin.services.example.net</code>. If an authorized private zone for <code>services.example.net</code> is the most specific zone match and contains the record, the subsequent lookup can return a private address. If the zone lacks that record, Cloud DNS can return <code>NXDOMAIN</code>. A record in the public zone does not automatically act as fallback for that VPC lookup.

Capture a baseline you can repeat after the change

From the affected VM, use <code>dig</code> or <code>nslookup</code> to query the application name and each CNAME target. Check A or AAAA according to the actual application query. Record the time, VPC, resolver, response code, alias chain, final address, and TTL. Also note which response policy or zone matches the target. Use an approved public resolver as a comparison for publicly intended names only.

After the change, repeat the query from the same workload and resolver. Locate the first hop with a different address or error, then check the zone binding, records, and response policies for that name. If a configuration change is needed, correct the conflicting names you manage and retest from the application that uses them. Google recommends consistent TTLs for CNAME chains you control.

Handle the separate ANY query change by record type

Google also announced that starting January 5, 2027, a public authoritative zone will return one matching record for an <code>ANY</code> query. If a script checks addresses or mail records, request A, AAAA, MX, or the specific record type it uses. For a full zone inventory, use an authorized record-set listing interface.

Sources

Frequently Asked Questions

Why does the public resolver work while the VPC returns an internal address or NXDOMAIN?

After the change, the VPC can match an internal policy or private zone when resolving a subsequent target. Check each target and the most specific matching zone for the required record.

Can I query private aliases through public DNS for comparison?

Use the external comparison only for names intended to be public. Query private names using an approved internal runtime and the resolver it uses.

Does this apply as shown if my VPC uses an alternative name server?

Check the outbound policy and actual recursive path first. The examples assume a VM using the metadata resolver with no alternative name server configured.