> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/technical/platform-setup/brand-custom-domain-setup.md). # Brand Custom Domain Setup Point your brand to your own domain for your MVNO brand. Connect your domain to Reach so customers use your brand URL. Choose nameservers (recommended) or a CNAME (fallback). ### Overview Reach can serve your storefront and My Account on your domain. You keep your existing email provider. You have two setup options: * **Update nameservers (recommended)**. Reach manages the DNS zone. * **Configure a CNAME (fallback)**. You keep DNS with your registrar. ### Default brand domain If you do not want to use your own domain, Reach will provide a default brand domain: * `www.brandname.thatsmymobile.com` This is the standard setup until your brand provides its own domain. ### Before you begin Have these ready: * Access to your domain registrar account * Your current email host details (Google Workspace, Microsoft 365, etc.) * The nameserver or CNAME values provided by Reach Plan for 10–30 minutes of work. DNS propagation can take up to 24 hours. ### Choose a setup method Use nameservers unless you cannot transfer DNS control. | Situation | Recommended | | -------------------------------------------------------- | ------------------ | | Root domain cutover is acceptable | Update nameservers | | You must keep existing DNS records managed outside Reach | Configure CNAME | | You are only connecting a subdomain | Configure CNAME | ### Option A — Update nameservers (recommended) Use this when you can delegate DNS to Reach. This is the lowest-risk setup long term. {% stepper %} {% step %} #### Log in to your domain registrar Examples: GoDaddy, Google Domains, Namecheap. {% endstep %} {% step %} #### Navigate to DNS/Nameserver settings Go to DNS Management or Nameserver Settings. {% endstep %} {% step %} #### Select Custom Nameservers Choose the option to use custom nameservers. {% endstep %} {% step %} #### Paste the four Nameserver values Use the four Nameserver values provided by Reach. For example: * `ns-0000.awsdns-00.org` * `ns-000.awsdns-00.com` * `ns-0000.awsdns-00.co.uk` * `ns-000.awsdns-00.net` {% endstep %} {% step %} #### Save changes Save your changes. Your registrar may show a confirmation screen — accept any warnings about transferring DNS control. {% endstep %} {% step %} #### Notify Reach Email `accounts@reachmobile.com` confirming the update is done. {% endstep %} {% step %} #### Allow for DNS propagation Allow up to 24 hours for DNS propagation. Reach will validate the setup and take your site live. Most propagation completes within 1–4 hours. {% endstep %} {% endstepper %} ### Option B — Configure a CNAME (fallback) Use this method only if you need to keep existing DNS records in place and cannot transfer Nameservers. {% stepper %} {% step %} #### Log in to your domain registrar {% endstep %} {% step %} #### Go to DNS Management Navigate to Domain Configuration or DNS Management. {% endstep %} {% step %} #### Add the CNAME record Add the CNAME record values provided by Reach. {% endstep %} {% step %} #### Save and confirm Save your changes and confirm to `accounts@reachmobile.com` that the CNAME has been added. {% endstep %} {% step %} #### Allow for DNS propagation Allow up to 24 hours for propagation. Reach will validate and go live. {% endstep %} {% endstepper %} ### Validate the cutover Once propagation is complete, run through this checklist to confirm your domain is set up correctly: * Your domain loads the branded storefront. * The browser address bar shows your domain. * SSL is active (lock icon). * Branded email still sends and receives. Reach provisions SSL after DNS is in place. Allow up to 1 hour after propagation completes. ### Email and DNS notes Reach does not host email. Your existing email provider (Google Workspace, Microsoft 365, or similar) remains completely separate and should not be affected by this process. To keep email running smoothly: * Keep your MX records pointing to your email provider — do not change these * Ensure your SPF, DKIM, and DMARC records are configured as recommended by your email host * Test sending and receiving emails before and after going live to confirm everything is intact Already using Google Workspace or Microsoft 365? No additional changes are needed. Your MX records will remain intact. ### DNS record types (reference) For reference, here is a summary of the common DNS record types you may encounter during setup. | **Record Type** | **Purpose** | **Example** | | --------------- | ---------------------------------------------------------- | -------------------------------------------------- | | NS | Delegates DNS management to Reach | ns-1234.awsdns-xx.org | | A | Maps your domain to a server IP address (managed by Reach) | Provided by Reach | | CNAME | Creates an alias pointing one name to another | shop → brand.reachmobile.com | | MX | Routes email to your email provider's servers | ASPMX.L.GOOGLE.COM | | TXT (SPF) | Validates that emails are sent from authorised servers | v=spf1 include:\_spf.google.com \~all | | TXT (DKIM) | Digital signature verifying email authenticity | google.\_domainkey | | TXT (DMARC) | Policy for handling emails that fail authentication | v=DMARC1; p=none; rua=mailto: | ### Troubleshooting * **Old site still shows after 24 hours** * Clear browser cache. * Confirm the registrar saved the change. * **Email delivery fails** * Confirm MX records still point to your email provider. * Confirm SPF includes your email host. * **SSL warning** * Wait up to 1 hour after propagation completes. * Refresh and re-test. * **Non-branded domain appears in the address bar** * DNS is not fully propagated. * Re-check after a few hours. ### Registrar navigation (quick reference) Use your registrar’s DNS screen to edit nameservers or add a CNAME. Common paths: * GoDaddy: Domains → Manage DNS → Nameservers * Namecheap: Domain List → Manage → Nameservers {% hint style="info" %} Questions or clarification? Reach out to your respective account manager or email at for help and support. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.reachplatform.com/technical/platform-setup/brand-custom-domain-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.