To redirect a domain whose DNS is at Google Cloud DNS, create the redirect in RedirHub, then in Cloud DNS point the root domain to RedirHub with an A record, add the TXT verification record, and point www with a CNAME. RedirHub detects the change and issues the SSL certificate automatically.
Cloud DNS only hosts DNS records. Redirecting a domain on Google Cloud usually means an HTTPS load balancer with a managed certificate. With RedirHub you only add DNS records; RedirHub serves the redirect over HTTPS.
Before you start#
- The DNS for your domain is managed in Google Cloud DNS. If your domain uses another provider's nameservers, make the changes there instead (how to check).
- A RedirHub account. The 14-day free trial is enough for this guide.
- About 10 minutes, plus time for DNS to update.
Step 1: Create the redirect in RedirHub#
In the RedirHub dashboard, open Redirects, click New redirect and choose Single import. Enter your domain, for example example.com, and click Next. Then set the destination URL, the Method (301 for a permanent move) and the Forwarded Options, and create the redirect.
You don't need to add www separately. A redirect for the root domain also covers www, including the same paths, as long as www points to RedirHub in DNS.
Need more detail on these options? See Setting Up URL Redirects and Redirect Methods Explained.
Step 2: Open Connect DNS in RedirHub#
Click Connect DNS in the notice that appears after you create the redirect, or open Hostnames and click Connect DNS next to the domain. Google Cloud DNS doesn't support automatic setup yet, so RedirHub opens the Manual tab. It lists each record with a copy button, plus any old record you need to delete.
| Host | Type | Value |
|---|---|---|
| @ (root domain) | A | 3.33.236.10 |
| @ (root domain) | TXT | Your verification value, e.g. rehd-verify=abc123.rediredge.com |
| www | CNAME | Your CNAME target, e.g. abc123.rediredge.com |
Step 3: Update the DNS records in Google Cloud DNS#
- In the Google Cloud console, open Network services → Cloud DNS and click your zone.
- Delete existing A, AAAA and CNAME record sets for the root domain and www. Keep NS, SOA, MX and other TXT records.
- Click Add standard: leave DNS name empty, type A, IPv4 address 3.33.236.10.
- Add a TXT record set with an empty DNS name and the value from your dashboard. If a root TXT record set already exists (for example SPF), edit it and add the value as another item.
- Add a CNAME record set with DNS name www and the canonical name from your dashboard.
For the root domain, leave DNS name empty. Only change A, AAAA and CNAME records for the root and www: your email (MX) and other TXT records keep working as before.
Step 4: Wait for Connected and HTTPS#
RedirHub checks the records automatically. Changes are often picked up within minutes but can take up to 24 hours, depending on the TTL of the old records. When the domain shows Connected, the redirect is live, and the SSL certificate status changes to Secured shortly after.
Step 5: Test the redirect#
Open your domain in a private browser window and check the homepage, a deeper page and the www version, over both http:// and https://. If something doesn't work yet, see Troubleshooting new redirects or how long DNS changes take.