I apologize for the lack of clarification on our end. We have resolved the incident as we are unable to provide a short-term fix for this. Instead, we have created a long-term investigation. We have also noted that this is a recent limitation of DNS resolvers and not necessarily an issue on our end.
We have clarified our response in the newest update on the post in Discourse: