Domain says "DNS check failed": what to check

Five quick checks that fix almost every domain stuck at "DNS configuration required".

A domain stuck at DNS configuration required or DNS check failed almost always comes down to one of five things. Work down this list.

1. Has it been long enough?

DNS changes usually show up within 10 minutes, but can take a few hours. Click Verify DNS on the domain's row in Settings > Domains after 10 minutes, then after an hour.

2. Is the Name field short?

Your domain company adds your domain to the end of the Name for you.

3. Is every character exact?

Copy and paste each value from Flourivate. One extra or missing letter, or a space at the end, is enough to fail. Compare the Name and Value side by side.

4. Is there an old record in the way?

• For a website domain, there should be exactly one A record with Name @. Delete or edit any other.
• Turn off Forwarding for the domain at your domain company.
• If you use Cloudflare, set the records to DNS only (grey cloud).

5. Is this domain meant to be live here at all?

If you only forward a domain somewhere else (for example an old business name that redirects to your main site), it will always fail the check, because it doesn't point at Flourivate. That's fine. Just make sure your real website domain is the primary:

1. Go to Settings > Domains.
2. On the row for the domain your site actually uses, click Set as primary.

You can leave the forwarded domain listed, or delete it.

Still stuck?

Send us a request from Help & Support > Create Ticket with a screenshot of your DNS records and of the domain row in Flourivate. We'll spot it quickly.