Hover DNS setup
If your domain is registered at Hover, connecting it to Redirect Supply means replacing Hover’s default and forwarding records with a few of your own. Your domain stays at Hover, and your registration and email forwarding don’t change. It takes about five minutes, plus a short wait while the changes spread.
Before you start
You need two things ready before you open Hover.
Add the domain in Redirect Supply
Add your domain in Redirect Supply first. Its settings page shows the records you’ll need, including a TXT value that’s unique to your domain. Keep that page open in another tab. This guide covers a root domain like brand.com. If you’re connecting a subdomain like go.brand.com, the DNS setup guide explains the differences.
Check your nameservers
Hover’s DNS records only control your domain when it uses Hover’s nameservers, ns1.hover.com and ns2.hover.com. If your domain points to Cloudflare or another provider, add the records there instead. The Cloudflare DNS setup guide covers the most common case.
Open DNS at Hover
All the changes in this guide happen in one section.
Find the DNS section
Sign in to the Hover control panel and select your domain. On the domain’s Overview page, open the DNS section. You’ll see every record on the domain and an Add a record button.
Records you’ll see there
New Hover domains point to Hover’s parking page with an A record on @ using the IP 216.40.34.41, often alongside a wildcard * record with the same IP. If you’ve used Hover’s forwarding, there are forwarding records as well. Not sure what else counts? The conflict table on your domain’s page in Redirect Supply lists every record that blocks the setup.
Clear the way
Before adding anything, remove what’s already pointing your domain elsewhere.
Delete Hover forwarding
Hover’s forwarding sends visitors on with a temporary redirect and sits on the same names Redirect Supply needs. Remove any forwarding set up for the domain, and delete any records that belong to it.
Delete the default and old records
Check the box next to the A record on @ that points to 216.40.34.41, the wildcard * record if you don’t use it for anything else, and any record on www. Open the Bulk edit dropdown, choose Delete, and confirm. More than one A record on @ would make your domain work only some of the time.
Leave email records alone
MX records and email TXT records like SPF or DKIM keep your email working, including Hover’s email forwarding. They don’t affect redirects, so leave them exactly as they are.
Add the Redirect Supply records
You’ll add four records with Add a record. In the Hostname field, enter @ for the root domain or just the prefix. Keep the default TTL.
Name | Type | Value |
|---|---|---|
www | CNAME | proxy.redirect.supply |
@ | A | 188.114.96.9 |
@ | A | 188.114.97.9 |
_cf-custom-hostname | TXT | Value from your domain’s settings page |
Add two A records for the root domain
Select Add a record and choose A. Enter @ as the hostname and 188.114.96.9 as the IP address, then save. Add a second A record with hostname @ and the IP 188.114.97.9.
Add the www CNAME
Add a CNAME record with hostname www and target name proxy.redirect.supply. Hover doesn’t allow a CNAME on @, which is why the root uses A records.
Add the TXT record
Add a TXT record with hostname _cf-custom-hostname and paste the value from your domain’s settings page in Redirect Supply into Content. On some less common domain endings, Redirect Supply also asks for an _acme-challenge TXT record. Add it the same way if you see it.
Check the list
Each record is saved as soon as you save its form. Look over the list to make sure all four are there and nothing still points to 216.40.34.41.
Check the status in Redirect Supply
Once the records are in, you’re done in Hover.
Check the conflict table
You don’t have to wait to find out if something’s wrong. Your domain’s page in Redirect Supply shows a conflict table with the records currently on your domain. Anything that blocks the setup, like the parking record or a leftover forwarding record, is flagged there along with what to do about it. Fix those first, and the rest is just waiting.
How long it takes
New Hover records are often picked up within an hour. Hover says changes can take up to 24–48 hours to spread fully.
When the domain goes Active
Redirect Supply checks your records automatically. When it finds them, the domain switches to Active and HTTPS is issued on its own, with no extra steps from you. See Domain statuses for what each status means along the way.
Hover-specific issues
Most problems on Hover come from leftover parking or forwarding records.
The domain still shows Hover’s parking page
The parking A record or the wildcard record is still in place. Delete everything pointing to 216.40.34.41 and check again in a private window after a few minutes.
The old forwarding still happens
A forwarding record is left on the domain. Remove the forwarding in Hover and delete its records, then clear your browser cache, because browsers remember redirects.
The domain works only some of the time
There’s more than one A record on @. Delete everything on @ except Redirect Supply’s two A records.
The domain is stuck on Pending
Open the conflict table on your domain’s page in Redirect Supply. It shows which record is blocking the setup, usually the parking record or an old www record. Remove what it flags and wait a few minutes. Record conflicts covers the common cases.