Quick answer
A custom domain shows Pending in Settings → Website → Domain while WanderOS waits for the DNS records to be in place and recognized across the internet. This applies to all WanderOS hosts. Most domains move to Active within a few hours. Some take longer because of DNS provider propagation delays. If your domain is still Pending after 48 hours, the most likely cause is an incorrect or missing DNS record at your registrar. The fixes below cover the common causes in order of likelihood.
What does each domain status mean?
Status | What it means | What to do |
Pending | DNS records have been requested but are not yet verified across the internet. | Wait. Check again in a few hours. |
Active | Your domain is verified and serving your WanderOS site. | Nothing — your site is live on the custom domain. |
How long should Pending take?
Most domains move to Active within 1 to 4 hours. Some take longer:
Up to 24 hours if your DNS provider is slow to propagate changes
Up to 48 hours in the worst case, especially for newly registered domains or domains using older registrars
Indefinitely if a required DNS record was never added or was added incorrectly
If you connected your domain less than 48 hours ago, give it more time before troubleshooting.
Common causes when Pending lasts more than 48 hours
Work through these in order. Most stuck-Pending cases come from one of the first three.
1. The DNS records were never added
If you set up DNS manually and forgot to add the records WanderOS needs, the domain will never move to Active. Log in to your DNS provider and confirm that the records WanderOS asked you to add are present.
2. The DNS records were added to the wrong domain
If you manage multiple domains, it's easy to add records to the wrong one. Check the domain name at the top of your DNS provider's panel and confirm it matches the domain you typed into WanderOS exactly.
3. An existing conflicting record is overriding the new one
If your domain already had an A or CNAME record at the same name, the new WanderOS record may be conflicting with the old one. Look for duplicates at @ (root) and www and remove any that point to a previous host.
4. DNS is technically correct but cached old values
Some local devices and corporate networks cache DNS heavily. Try loading your domain in an incognito window, or test on a mobile device that's on cellular data instead of Wi-Fi. If the site loads there but not on your laptop, your local DNS cache is stale and will refresh on its own within a few hours.
5. The domain is using DNSSEC and the records are unsigned
If you have DNSSEC enabled at your registrar, unsigned records can be rejected by some resolvers. Most hosts can resolve this by working with their registrar's support team.
How can I check what DNS records are live?
Use a free DNS lookup tool to see what the rest of the internet sees for your domain:
General lookup: whatsmydns.net — shows your domain's records from many locations worldwide
A and CNAME records: mxtoolbox.com/DNSLookup.aspx
Compare the live values to the values WanderOS asked you to add. If they don't match, fix them at your DNS provider.
When should I contact support?
Contact Wander support if:
Your domain has been Pending for more than 48 hours
You've confirmed the DNS records are correct using one of the tools above
You're not sure which records you should have
The Pending banner shows an error message you don't understand
We can verify the records on our side and confirm what's blocking activation.
Troubleshooting
Pending banner is still showing after I added the records: Wait at least 4 hours. If still Pending after 48 hours, run a DNS lookup to confirm the records are visible to the internet.
DNS lookup says my records are correct but Pending stays: Hard-refresh the WanderOS dashboard. If it still shows Pending after 24 hours of correct records, contact Wander support.
Domain works in incognito but not in my browser: Local DNS cache. Restart your browser, or wait a few hours for the cache to expire.
I'm seeing different results from different DNS lookup tools: Normal during propagation. Wait for the slower locations to catch up.
My old website still loads at the same domain: Either DNS hasn't propagated yet or you have a conflicting record at your old host. Confirm in your DNS provider that no leftover A or CNAME points to the previous platform.