Not sure why a cname record doesn't seem to be working

DNS & Network
#1

I copied a CNAME record from one of my domains to another. This one is existing, and works:
https://springboard.aclu.org/
(I see some ascii art that is the custom 404 message on our fastly instance)

I copied that CNAME record to this domain,
http://test.aclu.bz/
but I’m for some reason getting 310 redirected to aclu.org, instead of to fastly. What have I done wrong?

#2

A redirect is almost certainly coming from the origin server, eg. Fastly. This likely means that Fastly hasn’t registered that origin hostname (test.aclu.bz) as an authorized hostname for your fastly endpoint.

2 Likes
#3

Yes, you are right. Thank you for helping out a struggling noob! :slight_smile:

#4

I registered the domain (https://springboard.aclu.bz/) with my fastly service, and I can see in fastly’s preview that it’s showing the custom 404 as expected:
http://springboard.aclu.bz.global.prod.fastly.net/

but when I go directly to the domain name, I’m still getting redirected to aclu.org. Any idea why that might be?

thank you!

#5

it’s working now, must have just needed to propagate.

#6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.