Why isn't my redirect.name redirect working?
Updated
Most redirect.name failures come down to one of three things: the hostname isn't pointed at redirect.name's server, the TXT rule record is missing or misnamed, or DNS hasn't propagated yet. Check those three in order before assuming the service is broken.
1. Confirm the hostname points at redirect.name
redirect.name only works if the hostname you want to redirect resolves to its server. That requires a CNAME (or an A record where CNAME flattening isn't available).
| Type | Name | Value |
|---|---|---|
| CNAME | go.example.com. | alias.redirect.name. |
If your DNS provider doesn't support CNAME flattening at the apex (sometimes offered as an ALIAS or ANAME record), use an A record instead:
| Type | Name | Value |
|---|---|---|
| A | example.com. | 45.55.126.223 |
Common mistakes here:
- Pointing the CNAME somewhere else. If the hostname still resolves to your old host or a parking page, redirect.name never sees the request.
- Using a CNAME at the apex on a provider that doesn't flatten it. The record may be rejected or silently ignored. Switch to the A record above.
- Forgetting the trailing dots.
alias.redirect.name.andgo.example.com.are fully qualified; some providers append your zone automatically and some don't. If your provider handles the zone suffix, enter the short form it expects.
Verify with a DNS lookup:
dig go.example.com CNAME +short
You should see alias.redirect.name. (or the A record resolving to 45.55.126.223). If you see anything else, fix the record first — nothing downstream will work until this is correct.
2. Check the TXT record name and prefix
The redirect rule lives in a TXT record, and it must be named with the _redirect. prefix. This prefix is required because TXT and CNAME records can't coexist at the same name — the prefix keeps them apart.
| Type | Name | Value |
|---|---|---|
| TXT | _redirect.go.example.com. | Redirects to https://example.com/ |
Common mistakes here:
- Missing
_redirect.prefix. A TXT record atgo.example.cominstead of_redirect.go.example.comis never read. - Wrong hostname in the name field. The name must match the hostname you're redirecting, with the prefix in front. Redirecting
docs.example.comneeds_redirect.docs.example.com. - Rule text doesn't match the supported syntax. The value is read as plain English.
Redirects to https://example.com/works; free-form prose does not.
Verify the TXT record:
dig _redirect.go.example.com TXT +short
You should see your rule string. If it's empty, the record name is wrong or the record hasn't propagated.
3. Allow for DNS propagation
After you add or change records, wait for propagation — usually a minute or two, but it can take longer depending on your provider's TTL. Visiting the hostname immediately after saving often shows the old behavior or a failure that resolves itself shortly.
If it's been well past the expected window and lookups still return stale or empty results, check your provider's TTL setting and whether a previous record is cached.
4. Check for conflicting or shadowing records
Because the TXT and CNAME records must live at different names, a leftover record at the wrong name can interfere:
- An old A or CNAME record at the redirect hostname that still points elsewhere will win over the intended target.
- A TXT record without the
_redirect.prefix is ignored, so if you only created that one, no rule exists. - Multiple TXT records at the same name are allowed and can be intentional. Path-specific rules (
Redirects from ...) are tried first, and catch-all rules (Redirects to ...) only apply if no path rule matches. If a path rule is catching traffic you expected the catch-all to handle, that's the rule order working as designed — remove or adjust the path rule.
Quick diagnostic checklist
dig <hostname> CNAME +short→ should returnalias.redirect.name.(or the A record →45.55.126.223).dig _redirect.<hostname> TXT +short→ should return your rule string.- Wait a couple of minutes after any change before retesting.
- Remove any stale A/CNAME at the redirect hostname and any TXT record missing the
_redirect.prefix.
If all four pass and the redirect still fails, the issue is in the rule text itself — recheck it against the supported syntax (Redirects to, Redirects permanently to, Redirects from ... to ..., wildcards, and the explicit status codes 301, 302, 307, 308).