Hi, @jordonbaade, I was also curious what was done to resolve this and I checked the logs for what was changed.
Interestingly, there were read-only queries done by both @jen and @laura but no one made any changes. There was no ghost fixing on our part.
Also we were not able to reproduce the issue in our testing. The root domain was a 301 redirect to www and www was a 200 status.
If you see the issue again, it would help us to know more about what isn’t working. Are you getting a 404 response? Is it a DNS lookup failure?
If you do get a 404, we need to be able to find the HTTP response which returned the 404. The simplest way to do this is to send us the x-nf-request-id header which we send with every HTTP response.
There more information about this header here:
If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:
- the complete URL requested
- the IP address for the system making the request
- the IP address for the CDN node that responded
- the day of the request
- the time of the request
- the timezone the time is in
Similarly, if the issue is a DNS lookup failure, we’d be happy to troubleshoot. If there is a DNS lookup failure, please let us know what domain name isn’t being found.
To summarize, we didn’t change anything on our side and both domain names alway worked when we tested. If see this issue again or if there are other questions, please let us know.