Docs · for Web servant, or whoever holds the DNS login

Pointing your own domain at your Area portal

Every Area gets <slug>.supportrecovery.org on signup. If your committee already owns a domain, one CNAME record moves the portal onto it.

What you get without doing anything

Provisioning an Area immediately creates its subdomain — for example metro.supportrecovery.org — with HTTPS already working. Nothing below is required. A custom domain is worth it when the committee already prints a web address on literature racks and wants that address to keep working.

Add the record

  1. Sign in to the Area portal as an admin or web servant and open Setup → Area, step 1.
  2. Enter the domain you own, exactly as people type it (for example examplearea.org, or www.examplearea.org).
  3. At your DNS provider, create a CNAME record pointing that name at cname.supportrecovery.org.
  4. Leave TTL on automatic, and if your provider offers a proxy or "orange cloud" toggle, leave it enabled.
  5. Come back to the wizard and press Verify. The portal checks the live record and switches the domain on when it sees it.

The apex-domain catch

A CNAME cannot legally sit on a bare domain (examplearea.org with no subdomain) under the original DNS specification. Most modern providers work around this with CNAME flattening or an ALIAS record, and if yours does, a bare domain is fine.

If yours does not, use www.examplearea.org for the portal and set a redirect from the bare domain to it. Your DNS provider almost certainly offers that redirect as a separate, free feature.

Why verification cannot be skipped

The portal will not answer for a hostname until it has seen the CNAME itself. The verification columns are writable only by the platform, never by an Area admin, which means nobody — including us — can attach a domain to an Area that does not actually control it. Expect minutes, occasionally a few hours, for DNS to propagate.

Primary sources

← All guides