Configuring Custom Domain in Neostore
Custom Domain Configuration
Configuring a custom domain in Neostore typically takes place in the production environment to ensure a seamless, secure, and branded experience for your customers.
Domains to Reflect Your Brand
Customize Your Neostore URL Domains to Increase Security and Customer Confidence!
Neostore allows you to redirect your customers to a comprehensive set of prebuilt, hosted web pages optimized for collecting data and distributing cards in mobile Wallets applications. By customizing your URL domains, you can:
- Match your brand identity
- Decrease potential phishing
- Increase customer confidence and conversion
By default, Neostore uses its own domain to serve pages:
https://app.neostore.cloud/<tenantId>/<layout>
Example: https://register.molia.top/molia/mobile
However, it is possible to allow your brand to use its own domain, improving security and assuring customers they are communicating directly with your brand rather than falling prey to phishing websites.
All configurations must be done on the brand’s DNS server. Neostore manages the SSL certificate through Auth0, so there is no need for additional configuration on your part.
Steps to Configure a Custom Domain
Step 1: Request Custom Domain Configuration
Inform Neostore that you wish to use a custom domain name and specify the domain name or subdomain to be used. For example: register.molia.top
.
Step 2: Configure DNS Records
Neostore will provide you with custom DNS records to configure on your brand’s DNS server. After you have made the necessary modifications, Neostore will check and validate the configuration.
Step 3: Additional DNS Records
Once the initial DNS record is validated by Neostore, additional custom DNS records may be required. Neostore will send these new records for you to configure on your DNS server.
Example of DNS Entries to Modify
Below is an anonymized example of the DNS entries that need to be modified for the web part of Neostore:
Type | Key | Value | Remarks |
---|---|---|---|
CNAME | registration.example.com | app.neostore.cloud | Used by end-users to display the app |
TXT | asuid.registration.example.com | 621ECF9549EAE65BA089A426C8142E089EF4C6916FB9AB9F21C111F30D85E816 | Used by Azure for domain validation |
TXT | _acme-challenge.registration.example.com | 7xLnjbponxeyiXkNsdIdrheyHHGouoFmfOXVvO9OAf8 | Used by Cloudflare for certificate validation |
TXT | _cf-custom-hostname.registration.example.com | cdea2f9a-2a68-48ed-a83d-88403213a690 | Used by Cloudflare for domain validation |
By following these steps and configuring the DNS entries as shown in the example, you can ensure that your custom domain is properly configured, enhancing the security and branding of your Neostore-hosted pages.