DNS Setup

Recommended Method: Landingsite Nameservers

The simplest way to connect your domain is to point your nameservers to Landingsite. This gives Landingsite full control of your DNS, which means SSL certificates and DNS records are managed automatically.

Update your nameservers at your domain registrar to:

• ns1.landingsite.ai
• ns2.landingsite.ai
• ns3.landingsite.ai
• ns4.landingsite.ai

Once nameservers are pointed to Landingsite, you can manage DNS records (like TXT records for domain verification) directly through the AI editor or the domain settings page in your Landingsite dashboard.

If your domain is already live on Landingsite nameservers, you do not need to change them again just because another provider or registrar sends a generic setup reminder. Those reminders often appear because the domain was added to another service account without actually moving DNS there.

How DNS Records Work

When you use Landingsite nameservers, the following records are configured automatically:

• A Records: Your apex domain (e.g., yourdomain.com) points to Landingsite’s servers, which handle the redirect to www.
• CNAME Record: The www subdomain points to Landingsite’s hosting infrastructure.
• SSL/TLS: Certificates are provisioned and renewed automatically.

Adding Custom DNS Records

If you need to add custom DNS records (for example, TXT records for Google Search Console verification or email provider setup), you have two options:

1. Ask the AI editor: If your domain uses Landingsite nameservers, you can ask the AI in the editor chat to add the record for you. Just paste the record details and ask it to add it.
2. Domain settings page: You can add, edit, and remove DNS records directly from your domain settings page in the Landingsite dashboard.

For common root-domain verification records such as Google Search Console, the record usually looks like this:

• Type: TXT
• Host/Name: @
• Value: the full verification string from the provider

Do not add those verification values under DS or DNSSEC fields. They must be added as normal TXT records.

Landingsite-managed DNS supports common records such as A, CNAME, TXT, and similar standard entries. However, Landingsite does not currently support adding NS records for subdomain delegation inside the managed zone.

If you need a provider like Lovable, Cloudflare, or another service to control a delegated subdomain via NS records, the usual workaround is to move DNS hosting for the domain to a provider that supports NS delegation, then keep the website connected to Landingsite using the external DNS method instead.

If the domain is registered through Landingsite, you can move DNS hosting yourself by setting your own nameservers — see Using Your Own Nameservers.

DNS Propagation

After changing nameservers or DNS records, it can take 24 to 48 hours for changes to fully propagate across the internet. During this time, your site may be intermittently available depending on your location.

If your site is not loading after 48 hours, see DNS Troubleshooting.