> Moving your RestoreCord verify page to a new domain? Follow the safe order for callbacks, DNS and /setup so no member hits an Invalid Redirect URL error midway.

Source: https://restorecord.host/switch-verification-domain

# How to change your Discord verification domain safely

Moving from the default address, a preset or an old domain to a new one is easy to get wrong in the wrong order. Here's the order that keeps every member able to verify.

[Open my bots](https://restorecord.com/dashboard)[Setting up a domain for the first time?](https://restorecord.host/custom-domain-setup)

Short answer

Add the new domain plus /api/callback to your bot's OAuth2 redirects in Discord first, keeping the old one. Then add the new domain in RestoreCord's Add Custom Domain dialog, wait for it to turn active, test with a spare account and republish your verify message with /setup. Remove the old callback and DNS records last.

## When you'd switch

* You started on the default address or a free preset and now own a domain.
* Your community rebranded and the old domain no longer fits.
* You're letting a domain expire and need verification off it first.
* You want a different subdomain, say join. instead of verify.

## What can break, and why

Verification is a round trip: the member leaves Discord for your verify page, authorizes your bot on Discord, and Discord sends them back to the callback on your domain. Discord only sends them to callbacks you've listed. Change the domain before Discord knows the new callback, and every member mid-verification lands on an **Invalid Redirect URL** error. Remove the old callback too early, and anyone still clicking an old link fails the same way.

## The safe order

1. 1In the Discord Developer Portal, add the new domain plus /api/callback under OAuth2 → Redirects. Leave the current one listed.
2. 2In Dashboard → Bots → advanced settings, open Add Custom Domain and enter the new domain, or pick a preset on the Free Domain tab.
3. 3Create the CNAME to fallback.restorecord.com and any TXT records the dialog lists. Presets skip this step.
4. 4Wait for the status to read active, then verify a spare account on the new address.
5. 5Run /setup in Discord and republish the verification message.
6. 6Remove the old callback in Discord and delete the old DNS records.

When you save a different domain, RestoreCord releases the previous custom hostname from your bot automatically. You only need to tidy up the records at your own DNS provider.

## Errors you might meet

| Message or symptom                     | What it means                                            | What to do                                            |
| -------------------------------------- | -------------------------------------------------------- | ----------------------------------------------------- |
| Invalid domain format                  | The field got a full URL or a path instead of a hostname | Enter a bare hostname like join.yourserver.gg         |
| Domain already in use                  | Another RestoreCord account has this hostname active     | Remove it there first, or pick a different subdomain  |
| Invalid Redirect URL after authorizing | Discord doesn't have the new callback                    | Add your-domain/api/callback under OAuth2 → Redirects |
| Old button still opens the old domain  | The verify message wasn't republished                    | Run /setup and republish                              |

## Removing a domain entirely

**Remove Domain** in the same settings card detaches the domain from your bot. Treat it like any other switch: make sure Discord lists the callback for the address you're returning to, and republish the verify message afterwards so the button doesn't point at a hostname that no longer serves your page.

## Switching a bot that serves many servers

The domain lives on the bot, so one switch moves every server on that bot at once. Republish the verify message in each of those servers, not just the main one. If only one community should move, give it its own custom bot within your plan's limit instead.

New domain stuck before it turns active? Use the [pending domain checks](https://restorecord.host/domain-pending). Going to a preset? Read [free verification domains](https://restorecord.host/free-verification-domain) first, or return to [RestoreCord Domains](https://restorecord.host/).

## Domain switch, step by step

1. 1  
### List both callbacks  
Add the new domain plus /api/callback in the Discord Developer Portal and leave the current callback in place.
2. 2  
### Add the new domain  
Enter it in the Add Custom Domain dialog and create the DNS records it shows, or pick a free preset.
3. 3  
### Test and republish  
Once the status is active, verify with a spare account, then run /setup and republish the verification message.
4. 4  
### Clean up  
Remove the old callback from Discord and delete the old CNAME at your DNS provider.

## After the switch, confirm these

Tick them off before you tell members about the new address.

New status reads active

The dialog no longer lists any records to add.

Republished in every server

Each server on the bot shows a Verify button for the new domain.

Spare account verified

Role given, log entry written, address bar on the new hostname throughout.

Old callback and CNAME gone

Removed only after real members have verified on the new domain.

## Domain switch questions

### 

### 

### 

## Change the address, keep every member

RestoreCord moves your verification to the new domain while the backups, firewall and member list behind it stay exactly where they are.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
