Domain proxying not working after updating A record
We're moving from a site on Azure to a WordPress site on WPEngine. We also have a number of existing worker routes we want to keep running for the new location. We tested this setup on a test instance with a
I updated the A record to point to the new hosting and waited for things to propagate (according to DNSChecker.org and other tools) and the DNS seems to work fine and the WPEngine site loads. However, none of the worker routes for the root domain work and requests for the root domain don't show up in the Instant Logs or in the HTTP Traffic. It's like the domain isn't going through CF, although I'm pretty sure it is. I cleared the CF cache and my browser cache multiple times. I also tried running the domain through a CNAME record with no noticeable change.
You can see in the attached screenshot that requests to the root domain dropped off entirely soon after I updated the A record at around 9:30.
I verified there are no Page Rules or Firewall rules applied, the
Strangely, I also ran the beta Trace tool and it returned "hostname does not belong to your account."
All of the above still work fine for any of our subdomains, including the worker routes and Trace. It's just the root domain that's the problem. And when I switched the A record back to the previous site location on Azure, everything started working again. Requests show up in the logs, worker routes are processed, and the Trace tool even works again.
Any ideas what could cause this? Is it some kind of DNS caching thing?
I could simply give things more time to make sure they've propagated fully, but my client can't have their site not functioning for that amount of time. I've already rolled back the migration for tonight after spending a few hours on this.
Any suggestions would be great. Thanks!
test.I updated the A record to point to the new hosting and waited for things to propagate (according to DNSChecker.org and other tools) and the DNS seems to work fine and the WPEngine site loads. However, none of the worker routes for the root domain work and requests for the root domain don't show up in the Instant Logs or in the HTTP Traffic. It's like the domain isn't going through CF, although I'm pretty sure it is. I cleared the CF cache and my browser cache multiple times. I also tried running the domain through a CNAME record with no noticeable change.
You can see in the attached screenshot that requests to the root domain dropped off entirely soon after I updated the A record at around 9:30.
I verified there are no Page Rules or Firewall rules applied, the
cf-Strangely, I also ran the beta Trace tool and it returned "hostname does not belong to your account."
All of the above still work fine for any of our subdomains, including the worker routes and Trace. It's just the root domain that's the problem. And when I switched the A record back to the previous site location on Azure, everything started working again. Requests show up in the logs, worker routes are processed, and the Trace tool even works again.
Any ideas what could cause this? Is it some kind of DNS caching thing?
I could simply give things more time to make sure they've propagated fully, but my client can't have their site not functioning for that amount of time. I've already rolled back the migration for tonight after spending a few hours on this.
Any suggestions would be great. Thanks!
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Was this page helpful?
