- Newest
- Most votes
- Most comments
To verify your domain with Google using Route 53:
Open Route 53 and go to your domain's hosted zone. Create a new TXT record: Name: Leave blank for root domain verification. Value: Enter "google-site-verification=your_code_here". TTL: Set to 300 seconds or another preferred value. Save the record and go back to Google to complete verification. Wait a few minutes for the record to propagate, then click Verify on Google.
To configure the Google site verification for your domain in Amazon Route 53, you'll need to add a TXT record to your DNS configuration. Here's how you can do it:
-
Sign in to the AWS Management Console and open the Route 53 console.
-
In the navigation pane, choose "Hosted zones."
-
Select the hosted zone for your domain.
-
Choose "Create record."
-
For the record name, you should enter just the @ symbol or leave it blank. This represents the root domain.
-
For the record type, select "TXT" from the dropdown menu.
-
In the Value field, enter the entire verification string provided by Google, including the quotation marks: "google-site-verification=Gqvenw-CjovQ6WP7s_FH8WPo1DivP2TTGou-W0LQCMGU"
-
Leave the TTL (Time to Live) as default or adjust if needed.
-
Click "Create records" to save the new TXT record.
By using the @ symbol or leaving the name field blank, you're creating the TXT record for the root domain, which avoids adding any domain name suffix. This should allow Google to verify your site ownership correctly.
After adding the TXT record, it may take some time for the changes to propagate across the DNS system. Once propagated, you should be able to complete the verification process with Google.
Remember, if you encounter any issues, double-check that you've entered the verification string exactly as provided by Google, including any quotation marks.
Sources
Making Route 53 the DNS service for a domain that's in use - Amazon Route 53
Benefits of Domain Registration with Amazon Route 53 | Networking & Content Delivery
Relevant content
asked 2 years ago
The UI responds with:
Error occurred Please try again later. (UnknownError)
...if "Subdomain" is left blank. This, despite the UI stating explicitly "Keep blank to create a record for the root domain." @ creates an incorrect record (It will not create a TXT record for sampledomain.com, but a TXT record for @.sampledomain.com). As does a space. A dot (.) doesn't work.
Something in the UI does not work, and all it gives me is a nebulous error. Possibly it doesn't like two different TXT records for the base domain? No clue. This is a normal use case.