// CUSTOM DOMAINS
Configure DNS Records
What to point at AnySites, and how to tell propagation delay from a real failure.
Two different kinds of DNS records are involved, and it's easy to confuse them:
| Record | Who manages it | Purpose |
|---|---|---|
{project}.anysites.app (platform subdomain) | AnySites, automatically | Created the first time a deploy succeeds. You never touch this. |
| Your custom domain's TXT + routing record | You, at your own DNS provider | One-time setup when adding a custom domain — see Add a Custom Domain. |
Propagation vs. a real failure
DNS changes at your registrar can take anywhere from a few minutes to a few hours to propagate, depending on your provider and the record's TTL. Before assuming a custom domain is broken:
- Check the record actually saved at your DNS provider (typos are the most common cause).
- Use a DNS lookup tool from outside your own network — your ISP's resolver may have cached the old answer.
- If the record is correct and it's been over a few hours, check the domain's status on the project's Domains page rather than guessing from the browser error alone.