DNS Troubleshooting

If your domain is not loading or your site is showing errors after connecting to Landingsite, work through the following checklist.

Troubleshooting Checklist

Before you start: make sure you know which setup you are using.

Landingsite nameservers: ns1.landingsite.ai through ns4.landingsite.ai
External DNS: keep your current DNS provider and use only Landingsite’s two apex A records plus the www CNAME

Mixing both methods, or leaving out the www CNAME on external DNS, is a common reason SSL or verification gets stuck.

1. Is Your Website Published?

Your website must be published for it to be accessible at your domain. If you have not published yet:

Click the Launch button at the top right of the editor, or
Click the blue “Yes, continue” button in the AI chat when prompted.

An unpublished website may show a Landingsite 404 page or a “not published” status even if your domain is connected correctly.

Also make sure the website itself is on a paid Basic or Pro plan. A custom domain will not go live from a Free website even if the domain connection looks correct.

2. Are Your Nameservers Correct?

Your domain’s nameservers must be set to:

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

Check this at your domain registrar. If nameservers are still pointed to your old hosting provider or the registrar’s defaults, your domain will not connect to Landingsite.

3. Has DNS Propagated?

After changing nameservers, DNS propagation can take 24 to 48 hours. If you just made the change, give it time. A delay of a few hours is still normal. You can check propagation status using free tools like whatsmydns.net.

4. Did Your Email DNS Records Get Removed?

If you changed nameservers, email service on your domain may stop working until you re-add the necessary DNS records for your email provider.

If your email is already working at another DNS host, the safest option is usually to keep the current nameservers there and point only the website traffic to Landingsite using the external-DNS records. That way your existing mail records stay in place.

Common records to restore include:

MX records
TXT verification or SPF records
CNAME records used by your mail provider

If your domain now uses Landingsite nameservers, you can add these records from your domain settings or ask the AI editor to add them.

5. Are CAA Records Blocking SSL?

CAA records tell the internet which certificate authorities are allowed to issue SSL certificates for your domain.

If your DNS provider already has restrictive CAA records, Landingsite may be unable to finish SSL provisioning even when your A records and www CNAME are correct.

A common example is a domain that only allows certificates from another provider, such as:

0 issue "amazon.com"
0 issuewild "amazon.com"

If that happens, remove the blocking CAA records (or update them so they no longer restrict certificate issuance to the wrong provider), then wait for DNS propagation and try again.

6. Is Your SSL Certificate Active?

SSL certificates are provisioned automatically once your domain is connected and DNS has propagated. If you see an SSL error in your browser, it usually means propagation is not complete yet — or CAA records are still blocking issuance. Wait and try again.

Important: sometimes the domain dashboard can show an older SSL status such as SSL: N/A even while the live domain is already loading correctly over HTTPS. If the website opens normally in the browser with https:// and no certificate warning, treat the live domain as the source of truth first and the dashboard badge as possibly stale.

If your nameservers are already correct but SSL still looks stuck after 24 to 48 hours, check whether the website itself has been published. A domain can be connected correctly while the attached website is still unpublished.

If you are using external DNS on a root domain, also confirm all three records are correct at the same time:

A @ → 75.2.29.147
A @ → 166.117.246.71
CNAME www → proxy-ssl.getlandingsite.com

A very common failure case is the apex A records being correct while the www record is missing, still set as an A record, or pointing somewhere else. In that case, the domain may look partly connected while SSL or verification never finishes.

It is normal for your DNS zone to contain other records for things like email, Microsoft 365, Google Workspace, DKIM, SPF, verification, or other subdomains. You do not need to delete unrelated DNS records just because they are also CNAMEs or TXT records. Focus only on the website records for @ and www, and remove or replace records only when they conflict with those exact hostnames.

If you are connecting a subdomain with external DNS (for example offers.yourdomain.com), the setup is different:

use a single CNAME for that hostname pointing to proxy-ssl.getlandingsite.com
remove conflicting A, AAAA, or extra CNAME records for that same hostname
if the subdomain still loads from your old host, DNS has not fully switched yet even if Landingsite shows a pending-validation message

If your dashboard says the domain is already verified by another account, support may need to manually verify ownership and release the old connection before you can attach it to the correct website.

7. Try an Incognito Window

Your browser may be caching an old version of the site or an error page. Try loading your domain in an incognito/private browsing window or clear your browser cache.

8. Dashboard Says “Verifying Domain” but the Site Is Already Live

Sometimes the editor or dashboard can show an older domain status even after the domain is already connected and loading normally.

If your site opens correctly on the live domain but the editor still shows Verifying Domain, Waiting for nameserver change, or Setup Failed:

click Try Again in the domain area if that button is available
refresh the editor
close and reopen the website
try an incognito/private window
check the live domain directly instead of relying only on the editor badge

If the live domain works, the issue may just be stale status in the editor rather than an active DNS problem. This can include older labels like SSL: N/A, Verifying Domain, Waiting for nameserver change, or Setup Failed even after HTTPS is already working.

If the stale message is what is blocking access to your DNS settings for a domain that already uses Landingsite nameservers, contact support with a screenshot of the current domain page so we can check the domain record on our side.

Common Issues

Website Was Working but Stopped

If your website was live and suddenly stopped loading:

Check your subscription status. If your payment failed or subscription was cancelled, your site will go offline.
Re-publish your website. Sometimes a fresh publish resolves the issue. Go to the editor and publish again.
Look for a Landingsite 404 page. On custom domains, this usually means the domain is connected but there is no currently published site attached to it.
Check whether the domain is still attached to the correct website inside Landingsite. In some cases, the nameservers stay correct but the domain becomes disconnected from the website in your Landingsite settings. Open the website, go to Settings > Domain, and confirm the domain is still connected to that site.
Domain was transferred between sites or accounts? If the website was moved to a different account, or the domain was detached from the original site, reconnect the domain to the correct website and then publish again.
Deleted an old website and expected the domain to move automatically? Domain ownership/connection does not automatically jump to the replacement website. Open the new website, reconnect the domain in Settings > Domain, and publish again.

Domain Shows the Wrong Website

Only one domain can be connected to one website. If you recently moved your domain from one site to another, make sure you disconnected it from the old site first and then connected it to the new one.

Root Domain Works Intermittently or Loads Something Else

If www.yourdomain.com loads your Landingsite site but the root domain (yourdomain.com) is intermittent, redirects somewhere unexpected, or shows a different page, the DNS is often mixed between Landingsite and another provider.

Common causes:

extra A records still pointing to an old host
registrar-level forwarding still enabled on the root domain
a second DNS provider still managing the apex domain

For external DNS setups, the root domain should normally use only:

A @ → 75.2.29.147
A @ → 166.117.246.71
CNAME www → proxy-ssl.getlandingsite.com

Remove extra apex A records or forwarding rules that send traffic somewhere else, then wait for DNS changes to propagate.

For external-DNS subdomains, the same idea applies: keep only the required CNAME for that hostname and remove leftover A/AAAA records that still point to another host.

Domain Purchased Through Landingsite Not Loading

Domains bought through Landingsite should work automatically in normal cases. If yours is not loading:

Make sure the website is published.
Check the domain’s expiration date and renewal status in your Landingsite domain settings.
If the domain has expired, renew it first, wait for it to come back online, and then publish the website again.
If the domain is active and the site still does not load, contact support.

Still Having Issues?

If you have gone through all the steps above and your site is still not loading, contact our support team with your domain name and we will investigate.