Skip to content
Back to Blog
Guides5 min read

Setting Up Custom Verification Domains

Restore Hub Team·

Using a custom discord verification domain is one of the simplest ways to make your verification page look professional and trustworthy. Instead of sending members to a generic URL, you can point them to something like `verify.yourcommunity.com`—a branded experience that builds trust and increases verification completion rates.

This guide walks through the complete setup process, from DNS configuration to SSL provisioning, and covers the most common issues you might encounter.

Why Custom Domains Matter

Trust and Completion Rates

When members see a verification link, they make a split-second decision about whether to click it. A link to `verify.yourcommunity.com` is inherently more trustworthy than a link to a third-party domain they have never heard of. In communities where phishing awareness is high (which it should be), members are trained to be suspicious of unfamiliar URLs.

Server owners who have switched to custom domains report 15-25% higher verification completion rates. That is a significant number of members who would have otherwise bounced.

Brand Consistency

If your community has a website, social media presence, and Discord server, the verification page should feel like part of the same brand. A custom domain, combined with Restore Hub's visual customization options, creates a seamless experience from first click to verified member.

SEO and Discoverability

A custom domain means your verification page can be indexed under your own domain's authority. If someone searches for your community name, the verification page can appear in results alongside your main website.

Prerequisites

Before you start, you will need:

  1. A Restore Hub account with a Premium subscription (custom domains are a premium feature)
  2. A domain name you own and can manage DNS for
  3. Access to your DNS provider's dashboard (Cloudflare, Namecheap, GoDaddy, Route 53, etc.)

You do not need:

  • A web server or hosting account
  • Any coding knowledge
  • An SSL certificate (this is handled automatically)

Step 1: Choose Your Subdomain

We recommend using a subdomain rather than your root domain. Common choices:

  • `verify.yourcommunity.com` (most common and clearest)
  • `auth.yourcommunity.com`
  • `join.yourcommunity.com`
  • `discord.yourcommunity.com`

Using a subdomain keeps your main domain free for your website and avoids any DNS conflicts.

Step 2: Add the Domain in Restore Hub

In the Restore Hub dashboard:

  1. Navigate to your server's Verification Settings
  2. Click Custom Domain
  3. Enter your chosen subdomain (e.g., `verify.yourcommunity.com`)
  4. Click Save

Restore Hub will display a CNAME target—this is the value you need for the next step. It will look something like `verify.restorehub.net` or a similar endpoint.

Step 3: Configure DNS

This is the only technically involved step, and it is straightforward.

What You Are Doing

You are creating a CNAME record that tells DNS to route traffic from your subdomain to Restore Hub's verification servers. A CNAME record is essentially an alias—it says "when someone visits verify.yourcommunity.com, send them to the server at verify.restorehub.net."

DNS Configuration

In your DNS provider's dashboard, create a new record with these settings:

| Field | Value |
|-------|-------|
| Type  | CNAME |
| Name  | `verify` (or your chosen subdomain prefix) |
| Target / Value | The CNAME target shown in Restore Hub's dashboard |
| TTL   | Auto or 300 (5 minutes) |
| Proxy | Off / DNS Only (important for Cloudflare users) |

Cloudflare-Specific Note

If you use Cloudflare for DNS, you must set the proxy status to "DNS Only" (gray cloud icon, not orange). Cloudflare's proxy intercepts SSL and can conflict with Restore Hub's automatic SSL provisioning. Once SSL is provisioned, you can optionally re-enable the proxy, but it is safest to leave it as DNS Only.

Verification of DNS Propagation

DNS changes can take anywhere from 30 seconds to 48 hours to propagate, though most providers propagate within 5-15 minutes. You can check propagation status using:

  • dnschecker.org — Shows propagation status across global DNS servers
  • Command line: `dig verify.yourcommunity.com CNAME` or `nslookup verify.yourcommunity.com`

Wait until the CNAME resolves correctly before proceeding to the next step.

Step 4: Verify Domain Ownership

Back in the Restore Hub dashboard, click Verify Domain. Restore Hub will check that the CNAME record is correctly configured and points to the right target. If verification fails:

  • Double-check the CNAME target value (no typos)
  • Ensure you are using CNAME, not an A record
  • Wait a few more minutes for DNS propagation
  • If using Cloudflare, confirm the proxy is set to DNS Only

Step 5: Automatic SSL Provisioning

Once the domain is verified, Restore Hub automatically provisions an SSL certificate through Let's Encrypt. This happens within seconds and requires no action on your part.

The certificate:

  • Is issued automatically
  • Renews automatically before expiration (every 60-90 days)
  • Supports HTTPS with modern TLS (TLS 1.2 and 1.3)
  • Is trusted by all major browsers

After SSL is provisioned, your custom verification URL is live. Members visiting `https://verify.yourcommunity.com` will see your branded verification page with a valid HTTPS connection.

Step 6: Update Your Verification Link

Replace the old verification link in your server with the new custom domain URL:

  1. Update the verification channel embed or message
  2. Update any bot commands that reference the verification link
  3. Update your server's rules or info channels if they mention the verification URL
  4. Update any external links (website, social media) that point to the old verification URL

Troubleshooting Common Issues

"Domain verification failed"

Cause: DNS has not propagated yet, or the CNAME record is incorrect. Fix: Wait 15-30 minutes and try again. Verify the CNAME target matches exactly what Restore Hub shows.

"SSL provisioning failed"

Cause: Usually a Cloudflare proxy issue or a CAA record restriction. Fix:

  • If using Cloudflare, ensure proxy is set to DNS Only
  • Check if your domain has CAA records that restrict certificate issuance. Add `0 issue "letsencrypt.org"` to your CAA records if needed
  • Ensure no firewall is blocking port 80 (Let's Encrypt uses HTTP-01 challenges)

"Page shows a generic error or wrong site"

Cause: The CNAME is pointing to the wrong target. Fix: Verify the CNAME target value in your DNS settings matches the value shown in the Restore Hub dashboard.

"SSL certificate expired"

Cause: Automatic renewal failed, usually because DNS was changed after initial setup. Fix: Confirm the CNAME record is still correctly configured. Restore Hub will attempt renewal automatically. If the issue persists, remove and re-add the custom domain in the dashboard.

"Members report the page is slow"

Cause: DNS resolution is adding latency, or the DNS TTL is too high. Fix: Set the DNS TTL to 300 seconds (5 minutes) for optimal performance. If using Cloudflare with proxy enabled, the performance is usually excellent.

Best Practices

  • Use a subdomain, not your root domain, to avoid DNS conflicts
  • Keep DNS proxy off during initial setup, then optionally enable it after SSL is confirmed
  • Set a low TTL (300 seconds) so DNS changes propagate quickly if you need to make adjustments
  • Test the full flow after setup—visit the URL, complete verification, and confirm the role is assigned
  • Bookmark the Restore Hub dashboard so you can quickly check domain status if members report issues

Ready to set up your branded verification page? Get started free at restorehub.net and upgrade to Premium to unlock custom domain support.

Setting Up Custom Verification Domains — Restore Hub Blog | Restore Hub