This page describes how to register a domain using Cloud Domains. It walks you through a simple example of searching for an available domain, registering it, and then verifying the registration. Once you register a domain, Cloud Domains automatically renews it as long as your Cloud Billing account stays active.
Before you begin
Set up the following items in Google Cloud before you use Cloud Domains:
In the Cloud Console, go to the project selector page.
Make sure that billing is enabled for your Cloud project. Learn how to confirm that billing is enabled for your project.
Enable the API.
Register a domain
To register a domain, you must have the following permissions:
Permissions required for this task
To perform this task, you must have been granted the following permissions or the following IAM roles.
To register a domain, follow these steps:
- Step 1: Search for a domain name
- Step 2: Configure DNS for the domain
- Step 3: Choose privacy settings for your domain
- Step 4: Specify contact details
- Step 5: Verify registration
Step 1: Search for a domain name
- Go to the Cloud Console.
- Click Register domain.
- Search for an available domain. Identify the domain name that you'd like to purchase. Pricing is listed for each available domain.
Click Add add_shopping_cart. You can add as many domains as you like, subject to your available quota. For details, see the Quotas page. The total pricing based on your selection is calculated to the right. To remove a domain from your cart, click delete delete next to the domain name.
Step 2: Configure DNS for the domain
On the DNS configuration page, choose one of the following DNS providers. If you are registering multiple domains, you can choose individual settings for each domain.
DNS provider Description Cost Cloud DNS Google recommends that you use Cloud DNS as your DNS provider for all your name servers. Additional Cloud DNS charges apply. For details, see the Cloud DNS pricing page. Google Domains If you choose this option, you can configure your name servers through Cloud Domains, and then use Google Domains to configure the DNS resource records. Note that using Google Domains does not allow API access. No additional cost. Custom name servers Choosing the custom name server option enables you to set up your name servers using Cloud Domains, then configure your DNS resource records with a third-party DNS provider. Check with your DNS provider.
If you choose Cloud DNS, from the Cloud DNS drop-down, select the default New zone that is automatically created for the domain. To edit the zone name and other details, select Setup new zone, make the required edits, and click Save and Continue.
If you have already created a zone, Google Cloud chooses that zone by default.
If you choose Google Domains, select whether you want to enable or disable DNSSEC. For more information on DNSSEC, see DNS Security.
If you choose Custom name servers, enter at least two name servers. To add additional name servers, click Add another name server.
Step 3: Choose privacy settings for your domain
- By default, privacy protection is turned on. However, you can change the
settings to one of the following privacy options:
Privacy option Description Privacy protection on
Choosing this option ensures that your contact information is not available to the public. To help protect your contact information and prevent spam, a third party provides alternate (proxy) contact information for your domain in the public directory. The third-party provider forwards all messages that are sent to your proxy contact information to the actual private contact information.
Cloud Domains does not offer privacy protection for all domain endings or top-level domains (TLDs). Registries, the organizations that manage domain endings, have policies prohibiting the use of privacy protection for certain TLDs. To see privacy information for a specific TLD, click the TLD on the Supported TLD reference page. Privacy information for the TLD is available in the DNS reference section.
Limit your info available to the public Choosing this option makes limited personal contact information available to the public. The actual information available publicly depends on the domain that you have chosen. To see privacy information for a specific TLD, click the TLD on the Supported TLD reference page. Privacy information for the TLD is available in the DNS reference section. Make all contact info public Choosing this option makes all your contact information available to the public through the WHOIS database.
- If you choose to make all contact information publicly available, you must click I agree on the pop-up dialog.
- Click Continue.
Step 4: Specify contact details
Your contact information is necessary for ICANN to reach you if there are any problems. The information you enter becomes the public contact information for your domain in the WHOIS database. For more details, see Contact information.
Enter the contact details for the domain. By default, the same contact details that you enter are applied to the registrant, admin, and technical contacts. To enter different information for each type of contact, you can edit your contact settings later.
If you are registering more than one domain, you can choose to apply the same contact details to all domains or choose to enter different contact details for each domain.
Processing your registration can take a few minutes.
Step 5: Verify your contact information
After you register your domain, Cloud Domains sends a verification email to the address that you provided in your contact information for the domain. This email includes a subject line that states Action required: Please verify your email address.
You must verify your contact information within 15 days or your domain becomes inactive.
To verify your email address, do the following:
- Open the verification email from email@example.com.
Click Verify email now.
Once Cloud Domains verifies your contact information, a Google Domains page with the message that your email address has been verified is displayed.
If there is an error in verifying your contact information, see the Troubleshooting section.