Domain Missing from GCP Console After Google Domains Divestiture

by

Summary

We experienced a critical resource visibility failure where a recently purchased domain name vanished from the Google Cloud Console interface, despite active billing and successful DNS resolution prior to the incident. The domain appeared to be “missing” from all associated projects, leading to a total loss of administrative control and an inability to manage DNS records via the Cloud DNS API or Console.

Root Cause

The investigation revealed that the issue was not a deletion of the resource, but a mismatch in identity and service abstraction. The root causes were:

  • Service Decoupling: Following the divestiture of Google Domains to Squarespace, the domain registration lifecycle was moved to a separate administrative plane.
  • Identity/IAM Ambiguity: The user was searching within the Cloud Console (GCP), which manages Cloud DNS and Compute resources, rather than the Google Workspace or Squarespace Registrar identity layer where the ownership record resides.
  • Resource Shadowing: The billing account was correctly charging for the domain, but the “Domain Registration” resource is a non-GCP native resource that exists in a specialized management layer that does not always propagate visibility to standard GCP Project views.

Why This Happens in Real Systems

In complex cloud ecosystems, this phenomenon occurs due to:

  • Architectural Partitioning: Large cloud providers often separate Control Planes. The plane used for billing/provisioning is often distinct from the plane used for resource management (DNS/VMs).
  • Acquisitions and Migrations: When one company (Google) sells a business unit (Domains) to another (Squarespace), the Source of Truth for identity shifts, creating a “ghost” period where billing remains in one system while management moves to another.
  • Abstraction Leaks: Users assume that because a resource is “paid for via GCP Billing,” the management interface must also be within the GCP Console. This is a logical fallacy in distributed systems.

Real-World Impact

  • Operational Blindness: Engineers cannot perform emergency DNS updates (e.g., changing MX records or mitigating a DDoS attack) because the resource is invisible.
  • Increased MTTR (Mean Time To Recovery): Troubleshooting efforts are wasted on “searching” for a deleted resource rather than “accessing” a migrated one.
  • Financial Friction: Billing remains active, leading to unnecessary costs for a resource the user feels they no longer control.

Example or Code (if necessary and relevant)

# Attempting to list domains via gcloud often fails if the domain 
# is managed by a registrar rather than Cloud DNS.

# This command might return nothing even if the domain is "active"
gcloud dns managed-zones list

# The correct approach is to verify the WHOIS data and 
# identify the actual authoritative nameserver provider.
whois your-disappeared-domain.com

How Senior Engineers Fix It

Senior engineers approach this by verifying the Source of Truth rather than trusting the UI:

  • WHOIS Validation: Immediately perform a whois lookup to identify the Registrar of Record. This bypasses the cloud console’s potentially misleading UI.
  • Identity Mapping: Check if the domain is tied to a Google Workspace identity rather than a standard Google Cloud Project identity.
  • Audit Trail Analysis: Use Cloud Billing Reports to trace the exact SKU being charged. If the SKU points to a specific reseller or third-party service, the search area is redefined.
  • Out-of-Band Management: Instead of fighting the GCP Console, pivot to the identified registrar’s management portal to regain control.

Why Juniors Miss It

  • UI Dependency: Juniors tend to believe that if a resource is not visible in the Console UI, it does not exist.
  • Siloed Thinking: They assume that because a resource is tied to a Billing Account, it must reside within the same Project Hierarchy.
  • Tool Over-reliance: They rely on AI (like Gemini) or tutorials that assume a static, unified cloud architecture, failing to account for corporate divestitures or service migrations that break the traditional mental model of a “single pane of glass.”

Leave a Comment