Setup

How to Configure DNS for Custom Domains

This guide shows you how to configure DNS CNAME records for your custom domain to point to Userorbit, ensuring your domain is correctly linked and operational.

Before You Begin

  • You have access to your domain registrar or DNS provider's control panel (e.g., Cloudflare, Namecheap, GoDaddy, AWS Route 53).
  • You have identified your Userorbit custom domain target value. This is typically provided by Userorbit and often looks like custom.userorbit.com or a similar subdomain specific to your account.

Steps

  1. Understand CNAME Records — A CNAME (Canonical Name) record is a type of DNS record that maps an alias name to a true or canonical domain name. For custom domains, you will typically create a CNAME record for your subdomain (e.g., www, app) to point to Userorbit's infrastructure. Using a CNAME is crucial; avoid using an A record.
  2. Identify Your CNAME Target Value — Your Userorbit custom domain target value will be a specific address provided by Userorbit. For example, if you want your domain app.yourcompany.com to point to Userorbit, the target value might be custom.userorbit.com. Make sure to use the exact value provided to you.
  3. Access Your DNS Provider's Control Panel — Log in to your domain registrar or DNS hosting provider (e.g., Cloudflare, Namecheap, GoDaddy, AWS Route 53). Navigate to the DNS management section, which might be labeled "DNS settings," "Zone editor," "Manage DNS," or similar.
  4. Add a New CNAME Record — In your DNS management section, look for an option to "Add Record" or "Add new DNS record."
    • For Cloudflare:
      1. From your Cloudflare dashboard, select your domain.
      2. Go to the DNS section.
      3. Click + Add record.
      4. Select CNAME as the type.
      5. For Name, enter the subdomain you want to use (e.g., www, app). If you want to use the root domain (e.g., yourcompany.com), you might need to use @ or leave it blank, but using a subdomain is generally recommended for CNAMEs.
      6. For Target, enter the Userorbit CNAME target value (e.g., custom.userorbit.com).
      7. Ensure the Proxy status is set to DNS Only (grey cloud icon). Do NOT use "Proxied" (orange cloud) for this record, as it can interfere with SSL/TLS and routing.
      8. Click Save.
    • For Namecheap:
      1. Log in to Namecheap and go to your Domain List.
      2. Click Manage next to your domain.
      3. Go to the Advanced DNS tab.
      4. Under Host Records, click Add New Record.
      5. Select CNAME Record as the type.
      6. For Host, enter the subdomain (e.g., www, app).
      7. For Value, enter the Userorbit CNAME target value (e.g., custom.userorbit.com).
      8. Click the checkmark to save changes.
    • For GoDaddy:
      1. Log in to GoDaddy and go to your My Products page.
      2. Next to your domain, click DNS.
      3. Scroll down to the Records section and click Add New Record.
      4. Select CNAME as the type.
      5. For Name, enter the subdomain (e.g., www, app).
      6. For Value, enter the Userorbit CNAME target value (e.g., custom.userorbit.com).
      7. Click Add Record or Save.
    • For AWS Route 53:
      1. Open the Route 53 console.
      2. In the navigation pane, choose Hosted zones.
      3. Select the hosted zone for your domain.
      4. Click Create record.
      5. For Record name, enter the subdomain (e.g., www, app).
      6. For Record type, choose CNAME.
      7. For Value, enter the Userorbit CNAME target value (e.g., custom.userorbit.com).
      8. Leave TTL as default or set to a desired value (e.g., 300 seconds).
      9. Click Create records.
  5. Understand DNS Propagation Time — After you add or modify a DNS record, it takes time for these changes to propagate across the internet. This process, known as DNS propagation, can take anywhere from a few minutes to 48 hours, though it's often much faster. During this time, your domain might not immediately resolve to the new target.
  6. Avoid Common DNS Configuration Mistakes —
    • Using an A record instead of CNAME: Always use a CNAME record when pointing a subdomain to another domain name. An A record points to an IP address, which is not suitable for dynamically managed services like Userorbit.
    • Conflicting Records: Ensure there are no other CNAME or A records for the exact same subdomain you are trying to configure. Conflicting records will prevent your domain from resolving correctly.
    • Cloudflare Proxy Mode: If you are using Cloudflare, make sure the proxy status for your CNAME record is set to "DNS Only" (grey cloud). If it's "Proxied" (orange cloud), Cloudflare will try to proxy traffic, which can interfere with Userorbit's SSL certificate provisioning and routing.

Verify It Worked

After waiting for adequate DNS propagation time, you can verify your CNAME record is correctly configured using command-line tools:

  • On macOS/Linux (using dig): 
    dig your.custom.domain.com CNAME
    Look for a line in the ANSWER SECTION similar to: 
    your.custom.domain.com.  300  IN  CNAME  custom.userorbit.com.
  • On Windows (using nslookup): 
    nslookup -type=CNAME your.custom.domain.com
    Look for a line similar to: 
    your.custom.domain.com    canonical name = custom.userorbit.com

If the output shows your custom domain pointing to the Userorbit target value, your DNS is correctly configured. You can also try accessing your custom domain in a web browser.

Was this page helpful?