Skip to Content
Frontlane Studio
Knowledge Base
Domains February 15, 2025

DNS Configuration Guide

Step-by-step instructions for pointing your domain to Frontlane Studio, including nameserver and CNAME setups.

dns domains ssl cloudflare

Properly configuring DNS is essential for connecting your domain to your Frontlane Studio site. This guide covers both approaches: full nameserver delegation and CNAME-based setup.

This gives Frontlane Studio full control over your DNS, enabling features like automatic SSL, DDoS protection, and email routing.

  1. Log in to your domain registrar (GoDaddy, Namecheap, Google Domains, etc.).
  2. Find the Nameservers section.
  3. Replace the existing nameservers with the ones shown in your control panel dashboard.
  4. Save and wait for propagation (typically 1-24 hours).

Once propagation completes, SSL is provisioned automatically and your site goes live.

Option 2: CNAME Setup

If you need to keep your existing DNS provider (e.g., you manage email MX records separately), use the CNAME approach:

  1. In your DNS provider, create a CNAME record:
    • Host: www
    • Value: The target shown in your control panel (e.g., yoursite.hlabs.dev)
  2. For the root domain (@), some providers support CNAME flattening or ALIAS records. If not, you’ll need to use an A record pointing to our anycast IPs.

SSL Certificates

SSL certificates are provisioned automatically for both setup methods. We use Let’s Encrypt with automatic renewal — no manual intervention required.

For sites requiring Extended Validation (EV) or Organization Validated (OV) certificates, contact support to upload a custom certificate.

Email Configuration

If you use email on your domain (e.g., hello@yourdomain.com), make sure your MX, SPF, DKIM, and DMARC records are preserved. With nameserver delegation, we migrate your existing email records automatically. With CNAME setup, your email records remain untouched.

Verifying Your Setup

After DNS changes, use the DNS Check tool in your control panel to verify:

  • Domain resolves to the correct edge IP
  • SSL certificate is active and valid
  • No conflicting records