DNS setup guide
Once a domain is added to Redirect Supply, it needs a few DNS records pointed at our edge network before redirects go live. Which records depend on whether you're setting up an apex domain or a subdomain.
Why this step matters
Adding a domain in Redirect Supply doesn't move any traffic on its own, DNS is what actually routes requests to our edge network so your rules can run. Until these records are in place and verified, your domain sits in Pending status and nothing redirects yet.
Apex domain records
For an apex domain (e.g. example.com), your domain's settings page shows four records to add:
Name | Type | Value |
|---|---|---|
www | CNAME | proxy.redirect.supply |
@ | A | 188.114.96.9 |
@ | A | 188.114.97.9 |
_cf-custom-hostname | TXT | Custom |
CNAME: www
Name www, value proxy.redirect.supply. This routes the www version of your domain to our edge network.
A record: @ (first)
Name @, value 188.114.96.9. One of two IP addresses that route your apex domain (the bare, non-www version) to our edge.
A record: @ (second)
Name @, value 188.114.97.9. The second of the two required A records, both are needed together.
TXT: _cf-custom-hostname
Name _cf-custom-hostname, value auto-generated for your domain (shown on your settings page). This verifies domain ownership so we can issue and activate the connection.
Subdomain records
Subdomains need fewer records, just two:
Name | Type | Value |
|---|---|---|
www | CNAME | proxy.redirect.supply |
_cf-custom-hostname | TXT | Custom |
CNAME
Name matching your subdomain (e.g. store for store.example.com), value proxy.redirect.supply.
TXT: _cf-custom-hostname
Same purpose as on apex domains, ownership verification, auto-generated value shown on your settings page.
There's no A record step for subdomains, the CNAME handles routing on its own.
The extra SSL verification record
Occasionally a fifth record appears: a TXT record named _acme-challenge, with a unique value generated for your domain. This shows up when extra validation is needed to issue an SSL certificate, most commonly on less typical TLDs (like .agency or .ltd). If you see it, add it the same way as the others, it's required to finish activating HTTPS on that domain. If it doesn't appear, you don't need it, the standard four (or two, for subdomains) records are enough.
Name | Type | Value |
|---|---|---|
_acme-challenge | TXT | Custom |
TTL and existing records
TTL doesn't matter here, the default your DNS provider suggests is fine. If there's already a record at the same name, for example an existing A record at @ or a CNAME at www, replace it with the one shown above rather than adding a duplicate.
Once your records are in
Records are checked automatically, no need to manually trigger verification. Once everything matches, your domain's status flips from Pending to Connected, see Domain Statuses for what each status means along the way. If a domain gets stuck, Domain Stuck on Pending and SSL Certificate Issues cover the common causes.
Still stuck? Email support@redirect.supply.