Gandi DNS setup
If your domain is registered at Gandi, connecting it to Redirect Supply means turning off web forwarding and changing a few records in Gandi’s LiveDNS. Your domain stays at Gandi, and your registration and Gandi Mail don’t change. It takes about five minutes of work, though Gandi suggests allowing a few hours for changes to show everywhere.
Before you start
You need two things ready before you open Gandi.
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 that LiveDNS is in use
Gandi’s DNS Records tab only controls your domain when it uses Gandi’s LiveDNS nameservers. 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 Records at Gandi
All the changes in this guide happen in one tab.
Find the DNS Records tab
Sign in to Gandi and open Domain. Select your domain, then the DNS Records tab. You’ll see every record in the zone and an Add record button.
Records you’ll see there
Gandi domains usually start with records for Gandi’s own services: an A record on @ and a CNAME on www used for web forwarding or a parking page, plus records for Gandi Mail. The @ and www records are in Redirect Supply’s way. 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.
Turn off web forwarding
If web forwarding is set up for the domain, remove it in the domain’s settings. Gandi’s forwarding can override your DNS records, and it’s the usual reason a Gandi default page keeps showing up.
Remove old @ and www records
Delete the A records on @ and the record on www, using the delete icon next to each. Gandi notes that two CNAME records on the same name simply won’t work, and more than one A record on @ makes the domain work only some of the time. Remove any AAAA record on @ too.
Leave email records alone
MX records and email TXT records like SPF or DKIM keep your email, including Gandi Mail, working. They don’t affect redirects, so leave them exactly as they are.
Add the Redirect Supply records
You’ll add four records with Add record. In the Name field, enter @ for the root domain or just the prefix. Keep Gandi’s default TTL. Gandi advises against very low TTLs.
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 record, choose A, enter @ as the name and 188.114.96.9 as the IPv4 address, then select Create. Add a second A record for @ with 188.114.97.9.
Add the www CNAME
Add a CNAME record with the name www and the value proxy.redirect.supply. If Gandi shows the value with a dot at the end, proxy.redirect.supply., that’s expected and correct.
Add the TXT record
Add a TXT record with the name _cf-custom-hostname and paste the value from your domain’s settings page in Redirect Supply. 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 when you select Create. Look over the list to make sure all four are there and nothing else is left on @ or www.
Check the status in Redirect Supply
Once the records are in, you’re done in Gandi.
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 a forwarding record or a leftover www record, is flagged there along with what to do about it. Fix those first, and the rest is just waiting.
How long it takes
Gandi recommends waiting at least 3 hours before judging whether a change worked. New records are often picked up sooner.
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.
Gandi-specific issues
Most problems on Gandi come from web forwarding that’s still on.
A Gandi default page still shows up
Web forwarding is still active, or a default record is left on @ or www. Turn off the forwarding, delete the leftover record, and check again in a private window after a while.
Gandi won’t add the www CNAME
Another record already sits on www. Delete it first, then add the CNAME again.
Records have no effect
Your domain uses nameservers outside Gandi LiveDNS. Add the records with the provider your nameservers point to.
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 a forwarding record or an old www record. Remove what it flags and give Gandi a few hours. Record conflicts covers the common cases.