Domain and DNS issues
Use this guide when a custom domain is not opening, SSL is not ready, or a published page does not appear on the expected domain.
Common causes​
| Symptom | What to check |
|---|---|
| Domain does not open | DNS records may be missing or incorrect. |
| Only one version works | Check both root domain and www version. |
| Browser shows security warning | SSL may still be preparing or DNS is not fully connected. |
| Old website still appears | DNS may still point to the previous host. |
| Atomicat page opens on another domain | The page may be published to a different site. |
DNS checklist​
- Confirm the domain is connected to the correct Atomicat site.
- Open your DNS provider and compare the required records.
- Remove conflicting records that point the same host elsewhere.
- Check both root domain and www version if you use both.
- Wait for DNS propagation before retesting.
- Test in a private browser window.
SSL checklist​
SSL can take time after DNS is correct. If the domain was just connected, wait and test again later.
If SSL still fails:
- Confirm DNS records are correct.
- Confirm the domain is not proxied through a conflicting service.
- Confirm the page is published to the intended site.
- Contact support with the domain and screenshots.
Publishing and domains​
A page can only appear on the domain where it is published. If the page is missing, confirm the page domain and publish status in Publish a page.
Related docs​
Frequently asked questions​
How long does DNS take?
Some DNS changes appear quickly, but full propagation can take longer depending on your provider and previous records.
Why does www work but the root domain does not?
They are separate hostnames. Configure and test both if you want both to work.