Fastly error: unknown domain even when the domain has been added to the service

General
1

Hi,

We’re getting the following error even when the domain has already been added to the service.

Fastly error: unknown domain: wholistichealth.prlabs.com. Please check that this domain has been added to a service.

Details: cache-lga21985-LGA (151.101.0.249)

image
image2560×1291 265 KB

Please let us know what is missing/not correct with our setup. It was working fine before for the new subdomains that we added.

Thanks!

2

Hi @repoaccessriddellnet, at a glance, it looks like the domain is working. This might have just been a matter of propagation time, but is everything all right on your end?

3

FYI, this problem is often caused by the DNS configuration of the domain being incorrect. For example, if TLS is activated on the domain for x.sni.global.fastly.net but a DNS CNAME for the domain is pointed to w.sni.global.fastly.net, then this is the type of response which will be received for requests to that domain.

4

Hi @aspires and @kevin.fleming,

I was able to resolve this after following up with the Fastly support team. The root cause is exactly as Kevin described — our new domains don’t use the same TLS cert as the classic ones, so using the same CNAME as before didn’t work.

Thanks!