The troubleshooting page describes common issues that you might encounter while using Cloud Domains and tells you how to handle them.
Registering a domain
searchDomains API call shows a domain name as available, but
retrieveRegisterParameters shows it is not
searchDomains call checks a large space of possible domain names to
provide suggestions. It relies on an
availability cache that may be incomplete or out of date. The
retrieveRegisterParameters call, on the other hand, deals with only one domain
name at a time and provides up-to-date domain name availability
retrieveRegisterParameters shows a domain name as
Unsupported, but you can register it through the Google Domains website
Cloud Domains doesn't yet support all domains that are supported through the Google Domains website.
You cannot use preferred contact privacy mode with the domain you are trying to register
The available contact privacy modes depend on the ending of the domain name you
chose. Domain endings are administered by many different partner registries, and
some of these have unique behavior and requirements. For instance, some domain
endings do not allow contact privacy at all, and others redact certain parts of
your contact information from the public WHOIS registry. Prior to registration,
refer to the
supportedPrivacy field in the output of
retrieveRegisterParameters to determine which contact privacy modes are
supported for a given domain name. After registration, the supported contact
privacy modes are listed in the
supportedPrivacy field of the registration
During registration, a
registration resource seems to be stuck in
REGISTRATION_PENDING state should be short-lived, on the order of a few
minutes in most cases before transitioning to
ACTIVE. If a registration is
pending for more than a few hours, contact Google Cloud support.
During registration, a registration resource ends up in
When a domain registration fails, you can call
to check whether the domain is still available. If it is, you can delete your
registration and try to register again.
There are also a number of common data-quality issues that can cause your domain registration to fail. For example, if you are setting custom name servers when registering the domain, they may not be recognized as registered name servers by the controlling registry. To complete your registration, you can temporarily set your DNS provider to Google Domains and change it after registration.
If the problem persists, contact Google Cloud support.
You are getting a
Quota exceeded error while trying to register a domain
You might have exceeded the quota for the number of registered domains. For detailed information about quotas, see the Quotas page.
Registrant email verification
Why do you have to verify your email address after registering a domain?
Google is required to verify the email address of a new registrant whenever a domain is registered. Google sends the registrant an email with instructions for completing the verification. Failing to verify your email address within 15 days after registration results in domain suspension.
After registering a domain, you didn't get a verification email
If you have used the same registrant email address before with another domain name,
you may not need to verify the address again. You can check your verification
status directly on the registration resource, which shows
issue field if your verification is pending. You can trigger a resend
of the verification email by calling
configureContactSettings and setting the
registrantContact.email field, or by visiting the Google Domains registration
You registered a domain with the wrong registrant email address
If your registrant email address contains a typo or is otherwise inaccessible by the named registrant, you can edit the registrant email address on the Google Domains registration settings page. Note that changing the registrant email address will require identity confirmation through SMS or phone call to the registrant phone number.
If you do not have access to either the registrant email address or the phone number, use the form on the Google Domains support page to discuss alternate methods of identity verification.
Your domain got suspended due to lack of email verification
If your domain is suspended due to lack of email verification, your registration
resource will be in
state: SUSPENDED and the issue field contains
UNVERIFIED_EMAIL. In this case, call the
configureContactSettings API and
set or change the
registrantContact.email field to trigger a new confirmation
email, and follow the instructions in that email to complete email verification.
Once verification is completed, your domain's suspension is automatically
Changes to your contact configuration are not taking effect
Due to ICANN requirements, many types of contact changes require confirmation
from both the previous registrant and the new registrant. While changes that you
made are awaiting such confirmation, they are temporarily listed in the
pendingContactSettings field of the registration resource. To confirm pending
changes, the old and new registrants must follow the confirmation instructions
To resend change confirmations that may have been lost, you must repeat
configureContactSettings API call. You can also trigger resends on the
Google Domains registration settings
You are listed as the registrant contact, but have lost access to your domain
Registrants are considered to be the rightful owners of a domain registration. If you are listed as the registrant contact but have lost access to the domain, use the form on the Google Domains support page to contact the support team. After verifying your identity, the support team can reinstate your access.
You deleted a project and lost access to your domain
If you delete the project that contains your
Registration resource, you lose
access to the domain. You have a few recovery options. If you deleted the
project recently, you can restore
then export your domain to
Google Domains, and then delete your project again. Exporting the domain will
give you management access using the Google Domains
If you cannot restore your project, the registrant contact can reach out to Google Cloud support to gain access to the domain.
You made changes to your DNS configuration but the changes are not taking effect
Due to the nature of DNS as a distributed system, changes to DNS configurations often take a while to propagate to the entire internet. This is because DNS resolvers anywhere in the world can cache your old configuration for a length of time equal to that record's time-to-live (TTL). Thus, it may take the full duration of the old configuration's TTL for your new configuration to become fully visible. For Cloud Domains, changes to the DNS provider or name servers, and changes related to DNSSEC can often take up to a day to become fully visible across the internet.
You published DS records and now your domain is not resolving
Publishing DS records is the last step in enabling DNSSEC for your domain. To ensure your domain continues to resolve, DS records should generally be removed a day or two before changing your name servers or DNS provider. Similarly, new DS records should be published no sooner than a day or two after completing a name server or DNS provider change.
If problems resolving your domain coincide with changes to DS records, this may mean that your domain's DNS configuration is not properly signed by your DNS provider. You can remove the DS records to see if that fixes the problem, but note that like any other DNS change, removing the DS records can take some time (up to the TTL of the removed records) to take effect.
You chose Google Domains as your DNS provider, but cannot see your zone in Cloud DNS
Choosing Google Domains as your free DNS provider means that you must manage your DNS configuration using the Google Domains website. These DNS configurations are not visible in the Cloud DNS product, and do not provide API access for configuration. If you require API access, create a zone in Cloud DNS and configure your domain to use that zone.
You want to disable automatic renewals for your domain
All domains in Cloud Domains renew automatically. If you decide to
discontinue the renewal of your domain, you can call the
Exporting your domain means it can no longer be managed in
Cloud Domains. The domain can still be managed in Google Domains
until its current registration period expires.
Note that, even after exporting your domain, Cloud Domains continues to bill you monthly until the end of the domain's registration period.
You want to delete your domain and return it to the pool of available domains
If you want to delete your domain before your registration would otherwise expire, you can do so from the Google Domains registration settings page.
For information on how to delete a domain in Google Domains, see Delete a domain.
Deleting your domain in this way causes your
Cloud Domains registration resource to enter
Note that Cloud Domains continues to bill you monthly until the end of the domain's registration period.
You are still being billed for a domain that you exported, deleted, or transferred
Domain name registrations are sold in year-length increments. Like the rest of Google Cloud, Cloud Domains bills you monthly for the resources that you use. As such, the annual cost of a domain is divided into monthly increments. Even if you export, delete, or transfer your domain, you still owe the full balance for the year of domain registration that you purchased. See the Pricing page for details.
Import from and export to Google Domains
You cannot import a domain that you already have with Google Domains into Cloud Domains
Cloud Domains does not support importing domains from Google Domains at this time.
Can a domain be managed with Google Domains instead of Cloud Domains?
Yes. Even domains managed with Cloud Domains can use Google Domains for management tasks, with the exceptions of billing and permission management. Note that to renew your domain after exporting, you must be in one of Google Domains' supported countries.
If you wish to also manage billing and permissions with Google Domains, call
export method on your registration resource.
Note that this process is not currently reversible. After exporting the domain to Google Domains, to make sure your domain doesn't expire, you must turn on automatic renewals.
You domain was exported to Google Domains and some people lost access
Cloud Domains uses IAM to manage permissions to domains, whereas Google Domains has its own separate permission system. When you export a domain from Cloud Domains to Google Domains, the account performing the export operation becomes the sole owner of the domain in Google Domains. That account can subsequently share access to the domain with other accounts using the Google Domains registration settings page.
Transfers to and from other registrars
You want to transfer your domain from another registrar to Cloud Domains
Cloud Domains does not support transfers of domains from other registrars at this time.
You want to transfer your domain from Cloud Domains to another registrar, but cannot access your transfer authorization code
Cloud Domains does not allow transfers to other registrars within the first 60 days of registration. You can contact Google Domains support to request an exception.
If you have crossed the 60-day limit, see Getting or resetting an authorization code.
Your domain stopped working and has
When your registration resource is in
state: SUSPENDED, you can generally find
more information in the
issues field. The most common cause of suspension is
issues: UNVERIFIED_EMAIL. See the Registrant email
There are many other possible causes of domain suspension. If you see
issues: CONTACT_SUPPORT on your registration resource, contact the
Google Cloud support team to learn more about the domain
- To learn more about features, see Cloud Domains overview.
- To resolve errors, see Error messages.
- To access API information, see Cloud Domains API.
- To get additional help, see Support.