We are experiencing an issue with Cloud DNS CNAME chasing in multiple zones.
Resolved
Minor
January 21, 2021 - Started almost 5 years ago
- Lasted about 1 year
Incident Report
Description: Mitigation work is currently underway by our engineering team.
The following zones are known to be impacted:
asia-east1-a
asia-east2-c
asia-northeast1-a
asia-northeast2-c
asia-northeast3-c
asia-south1-a
asia-southeast1-a
asia-southeast2-c
australia-southeast1-a
europe-west1-c
europe-west2-a
europe-west3-a
europe-west6-c
southamerica-east1-a
us-central1-d
us-east1-d
us-west1-a
us-west2-c
us-west3-c
us-west4-c
We do not have an ETA for mitigation at this point.
We will provide more information by Thursday, 2021-01-21 17:30 US/Pacific.
Diagnosis: CNAME chasing between private zone to private zone is not working.
Workaround: None at this time.
Components affected
Google Cloud DNS
One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.
Latest Google Cloud outages