Fastly Error: Unknown Domain
Quick answer
Visitors see 'unknown domain' when DNS already points at Fastly but the hostname is not added to an active service. Add the domain to the service and activate it.
Most likely fix: Add the domain and activate
How to fix it
Try these in order — the most common fix is first.
1. Add the domain and activate
- Log in to the Fastly control panel and open the service
- Click Clone to edit, then Domains, and add the exact hostname
- Activate the new version on Production
- Reload the site after a minute
Did this fix it?2. Test before switching DNS
- Look up a Fastly POP IP with dig on your domain or dualstack.nonssl.global.fastly.net
- Add a temporary hosts file entry for the domain, for example 151.101.0.204 www.example.com
- Open the site, then remove the hosts entry once the real CNAME points to Fastly
Did this fix it?3. Check the CNAME value
- In Domains, click View/edit and copy the CNAME under DNS details
- Run dig www.example.com +short and confirm it returns a Fastly hostname
- Use a subdomain such as www: CNAME records cannot be used on an apex domain
- If you use a wildcard CNAME, add the matching domains to the service too
Did this fix it?
Symptoms
Browser shows a Fastly error page saying unknown domain for your hostname.
Why it happens
- The CNAME was switched to Fastly before the domain was added to a service
- The domain was added to a service version that is not activated
- The hostname in the request differs from the domain added (for example www vs apex, or a missing wildcard domain)
- The service was deactivated or deleted but the CNAME still points to Fastly
This guide also covers
- fastly error unknown domain
- fastly unknown domain
- fastly error: unknown domain
Still not working?
If Fastly keeps failing, you're not alone. See every Fastly problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usThe same problem in other apps
All not loading, error messages & connection guides →
Cloudflare Error 521: Web Server Is Down (Cloudflare)
Other Fastly errors
- Fastly 503 Backend Read Error / Connection Timeout
- Fastly Purge Not Working (Old Content Still Served)
- Fastly TLS Certificate Stuck Pending or Not Provisioning
- Fastly Origin TLS Errors: Hostname Mismatch, Unable to Verify Certificate
- Fastly Not Caching: Always X-Cache MISS
- Fastly Serves Wrong Content or Denies Requests From Origin (Override Host)
- How to Cancel Fastly Account