Set up a Custom Domain

DNS records are essential for enabling users to access the services under your domain. If you have critical services running on your domain, please follow each step of this guide carefully. Incorrectly modifying DNS records can make your existing services inaccessible.

Introduction #

Custom domains are an excellent way to strengthen your brand, improve click-through rates, and provide a seamless experience for your audience. You can use any domain (or its subdomains) that you own as a custom domain. There are two prerequisites for creating a custom domain:

  1. The domain or subdomain must not be used for another purpose. For example, if your website is hosted at example.com, you cannot use example.com as a custom domain. However, you can use a subdomain of example.com, such as go.example.com.
  2. You must be able to modify the DNS records for your domain. If you are using a subdomain (e.g., go.example.com) as your custom domain and the root domain (e.g., example.com) is currently used for another purpose, be careful not to accidentally modify any DNS records for the root domain. Doing so could cause your root domain to stop functioning properly.

Step 1: Add the domain or subdomain #

In the Spiffylinks dashboard, navigate to Settings → Custom Domains and create a new custom domain. Enter just the domain (e.g., example.com, go.example.com). Do not include a scheme (e.g., https://) or anything else.

Step 2: Create the TXT Record #

After you add the domain, a TXT record value will be generated. This record must be created in your domain’s DNS settings – it allows us to verify that you own the domain.

  1. Copy the TXT record value.
  2. Navigate to your domain’s DNS settings and create a record with the following properties:
    • Type: TXT
    • Name/Hostname/Host: [your custom domain]
      • Depending on the registrar, you may be prompted to enter your custom domain in full or to enter only the subdomain portion. Pay close attention to what is prompted.
        • If you are prompted only for the subdomain portion, leave it blank if your custom domain is the root domain (i.e., blank for example.com) or fill it in if your custom domain is a subdomain (i.e., go for go.example.com).
        • If you are prompted for the complete domain, enter the complete custom domain.
    • Value: [your TXT record value]
    • TTL: 300 seconds
  3. Go back to the Spiffylinks dashboard and click the “Verify TXT Record” button. Our system will check your DNS records for the TXT record. Note that DNS records can take up to 24-48 hours to propagate, but typically take less than 5 minutes.

Step 3: Set the NS Records #

Once your TXT record has been verified, it is time to add the NS records.

a.ns.spiffylinks.com
b.ns.spiffylinks.com
c.ns.spiffylinks.com
d.ns.spiffylinks.com
  1. Copy the NS record values above.
  2. Navigate to your domain’s DNS settings and set the NS records for your custom domain. If your custom domain already has NS records defined, you should modify those existing records instead of creating new ones.
    • Type: NS
    • Name/Hostname/Host: [your custom domain]
      • Depending on the registrar, you may be prompted to enter your custom domain in full or to enter only the subdomain portion. Pay close attention to what is prompted.
        • If you are prompted only for the subdomain portion, leave it blank if your custom domain is the root domain (i.e., blank for example.com) or fill it in if your custom domain is a subdomain (i.e., go for go.example.com).
        • If you are prompted for the complete domain, enter the complete custom domain.
    • Values:
      • a.ns.spiffylinks.com
      • b.ns.spiffylinks.com
      • c.ns.spiffylinks.com
      • d.ns.spiffylinks.com
    • TTL: 300 seconds
  3. Head back to the Spiffylinks dashboard and click to confirm that you have set the NS records.

Step 4: Wait for setup to complete #

After you click to confirm that the NS records have been created, the automated setup process will begin. This typically takes 20 to 40 minutes. Your custom domain will be active once the setup process is complete.