> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://helpdesk.tiiny.host/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Common custom domain problems

If your domain isn't validating, start with **Analyze Issues** — it checks your specific setup and tells you what's wrong, rather than you working through DNS settings by hand.

GGo to **Custom Domains →** your domain **→ Details**, then click **Analyze Issues**. 

![The Analyze Issues button on a custom domain's details page](https://storage.crisp.chat/users/helpdesk/website/-/5/9/d/3/59d32bdaa5d1c000/image\_t91z1c.png)

If that doesn't resolve it, here are the three most common causes.

### 1. The CNAME name needs a suffix
Some domain registrars require you to add your domain as a suffix on the record's Name/Host value, rather than just the short name shown in your Tiiny Host dashboard.
* If the Name is `abcdef`, try adding it as abcdef.yourdomain.com.
* Some registrars also require a trailing dot: abcdef.yourdomain.com`.`

### 2. DNS changes haven't propagated yet

DNS updates take time to spread across the internet — usually around 15 minutes, occasionally longer.

Check at [dnschecker.org](https://dnschecker.org). If your records show as correct there but Tiiny Host still won't validate, wait a little longer and click **Validate** again.

### 3. A CAA record is missing

Some registrars need an additional CAA record before they'll allow validation:
| Field | Value |
| Type | CAA |
| Name | @ |
| Tag | issuewild |
| Flag | 0 |
| CA Domain | amazon.com |

### Provider-specific quirks
Most registrars work the same way, but a few have their own quirks worth knowing about.

###### Hostinger
If you're using Hostinger and validation isn't going through:
1. Confirm your CNAME record points to the correct target shown in your Tiiny Host dashboard.
2. Check the CNAME name format — Hostinger may need the suffix described above.
3. If you're hosting at the root domain, check there's an A record for `@` pointing to `18.168.91.127`.
4. Add the CAA record shown above.
5. Check propagation at [dnschecker.org](https://dnschecker.org). With Hostinger, this can take up to 48 hours.

If it's still not working, Hostinger support can check for account-specific issues on their end. 
Alternatively, [buying your domain directly through Tiiny Hos](https://helpdesk.tiiny.host/en/article/buying-a-domain-through-tiiny-host-tzyl67/)t avoids registrar-side DNS setup entirely.

###### Wix
Wix (and a small number of other registrars) won't accept a wildcard (`*`) as a CNAME value, which can cause the connection to fail. If that's happening:
1. Delete the custom domain from your Tiiny Host dashboard.
2. Click **Add new** in the Custom Domain section and re-enter your domain.
3. Click **Use subdomain** and enter `www`.

### My root domain isn't redirecting (e.g. yourdomain.com doesn't load, but www.yourdomain.com does)
We connect domains using CNAME records, which only work for www.yourdomain.com or another subdomain, not the bare root domain (`yourdomain.com`). 
To make the root domain automatically redirect to the `www` version, add this record:
| Field | Value |
| Type | A Record |
| Host | @ |
| Value | 18.168.91.127 |

Once this is set up correctly, yourdomain.com and https://yourdomain.com will both automatically redirect to https://www.yourdomain.com.
Visitors won't notice any difference.

### Still not working?
If you've worked through the steps above and your domain still isn't validating, please email us at support@tiiny.host with:
* Your domain name
* Your domain provider (registrar)
* A screenshot of your DNS records page