Custom verify domain stuck on pending? Check these
The dialog still says pending and members are waiting. Nine times out of ten it's a DNS detail. Work through these checks in order before you delete anything.
Short answer
A RestoreCord custom domain stays pending until the CNAME points to fallback.restorecord.com and every TXT record from the dialog exists. Check for typos, a doubled domain in the name field or an old A record on the same hostname, then allow up to 24 hours for DNS to propagate.
What pending actually means
RestoreCord activates your domain once the hostname is confirmed and its certificate is live. Until then the dialog keeps listing what's missing. Pending isn't an error, it's RestoreCord telling you it's still waiting on DNS. The job is to find out which record it can't see yet.
The CNAME points somewhere else
The CNAME for your subdomain must point to fallback.restorecord.com, and nothing else. Typos, a missing letter or an extra word at the end all block it. So does an older A or AAAA record on the same name, because a hostname can't have a CNAME alongside other records. Delete anything else on that hostname.
The name field doubled up
Most DNS providers add your root domain automatically. For verify.yourserver.gg the name is usually just verify. Typing the whole thing can quietly create verify.yourserver.gg.yourserver.gg, which RestoreCord will never find.
TXT records are missing
While the domain is pending, the dialog can list TXT records for ownership and certificate validation. Add every one exactly as shown, including long random values. Once a record has been checked, it disappears from the list, which is a handy way to see progress.
Your DNS provider is proxying the record
Some providers offer to proxy traffic through their own network, shown as an orange cloud or a proxy toggle. If validation stalls while the CNAME is proxied, switch it to DNS only so the record is visible as a plain pointer to the fallback address.
Checking the records yourself
You don't have to guess what the world sees. Public DNS lookup tools, or the command-line tools already on your computer, show the CNAME and TXT records for your subdomain. Compare the answer with the dialog character by character.
# macOS / Linux
dig +short CNAME verify.yourserver.gg
dig +short TXT <name from the dialog>
# Windows
nslookup -type=CNAME verify.yourserver.gg
nslookup -type=TXT <name from the dialog>- The CNAME lookup should return fallback.restorecord.com.
- Each TXT lookup should return the exact value from the dialog.
- No answer at all means the record isn't published yet or sits on the wrong name.
- An old value means the previous record is still cached. Wait for it to expire.
Pending domain cheat sheet
| Symptom | Likely cause | Fix |
|---|---|---|
| Pending after a few minutes | Normal propagation | Wait. It can take up to 24 hours |
| Pending after a full day | Wrong CNAME target or name | Compare each record to the dialog |
| TXT records never disappear | Value pasted incompletely | Copy it again from the dialog |
| Active, but verify errors out | Callback missing in Discord | Add your-domain/api/callback under OAuth2 |
Resist deleting and re-adding the domain. It restarts validation and can produce new TXT values to add, so you end up further behind.
Active, but members still can't verify
- Add your domain followed by /api/callback under OAuth2 → Redirects in the Developer Portal.
- Republish the verify message with /setup so the button points at the new domain.
- Test in a private window, which rules out an old cached page.
Starting from scratch? The full custom domain walkthrough covers every step. Tired of waiting on DNS? A free preset domain is active instantly while you sort it out, or head back to RestoreCord Domains.
Pending domain questions
Get your domain over the line
Once the records check out, RestoreCord issues SSL automatically and your verify page goes live on your own address.