DNS Settings / Custom Domains

Article author
Duncan Hamra

This guide will walk you through the steps to configure custom domains in Memberstack. This process is essential for implementing custom domains for your social auth providers and your single sign-on connections.

Note: You must have any paid plan to use this feature. 

If you are having trouble getting your DNS settings to work please make sure you are using your root domain and not a subdomain. This is important even if your app url is using a subdomain.

 

Step 1: Enter Custom Domain

1. Navigate to your Memberstack dashboard.
2. Click on 'Settings' and then 'Application'.
3. Scroll down to 'DNS Settings'.
4. Enter the custom domain you'd like to use in the first input field.
5. In the second input field, enter the subdomain you want to use for the hosted login screen. This applies to the single sign-on process.
6. Click 'Save'.

Step 2: Update DNS Records

1. You need to add a CNAME record for 'memberstack-clients' and point it to 'service-client.memberstack.com'.
2. Add another CNAME record for 'login' and point it to 'service-auth.memberstack.com'.
3. Make sure the proxy is off if your DNS service has one.

Step 3: Update Memberstack Header Script

1. Copy the new header script provided in the DNS settings on Memberstack.
2. Go to your website settings (in this example, Webflow is used) and replace the previous header script with the new one.
3. Save and publish your site.

Step 4: Reconfigure Social Auth Providers and Single Sign-On

1. Navigate to your social auth provider's developer console (Google is used in this example).
2. Go to the 'OAuth consent screen' and click 'Edit App'.
3. Under 'Authorized domains', add your own domain and click 'Save and Continue'.
4. Go to 'Credentials' and click on your 'Client ID'.
5. Add another 'Authorized redirect URI' and delete the previous one. The new URI should be 'memberstack-client.yourdomain.com/auth/callback'.
6. Click 'Save'.

Now, when you navigate to your site and pull up the login screen, you should see your own domain. The single sign-on login screen should also be provided through your own domain.

If you have any questions or run into any issues, feel free to reach out to our customer support team.

Was this article helpful?

Comments

2 comments

  • Comment author
    MJ Petroni

    Why would we want to use custom domains? Will this be necessary for multi-site login or something similar? Just trying to future-proof my initial setup. 

    0
  • Comment author
    Duncan Hamra

    Hey MJ Petroni 👋

    You are correct that this feature is most helpful when using Memberstack across multiple sites/domains. It is not a requirement. 

    0

Please sign in to leave a comment.