Pages DNS cache with prior 301
We have switched createiq.tech's apex domain to use Cloudflare Pages, but this is still returning a cached 301 from the origin:
We don't control the www.linklaters.com origin (which is what the CNAME was pointing to previously) and had no idea this was serving a 301. I would expect now that I've updated the record in Cloudflare for it to return the Cloudflare Pages site (regardless of the problematic previous 301 affecting clients, which we will need to deal with separately)
The domain is set up in the pages config and I've verified the DNS setup as well, as a proxied CNAME to the pages.dev domain. Using any other domain works fine, it's just this previous cached resolution that's problematic
We don't control the www.linklaters.com origin (which is what the CNAME was pointing to previously) and had no idea this was serving a 301. I would expect now that I've updated the record in Cloudflare for it to return the Cloudflare Pages site (regardless of the problematic previous 301 affecting clients, which we will need to deal with separately)
The domain is set up in the pages config and I've verified the DNS setup as well, as a proxied CNAME to the pages.dev domain. Using any other domain works fine, it's just this previous cached resolution that's problematic
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
