There is a website that is distributed through Azure CDN. The CDN endpoint was used as the destination of the CNAME entry for
www.< EXAMPLE >.com with the use of Google DNS. The website's www address works fine with one exception, Twitter cannot resolve the address
https://www., therefore, cannot read meta tags to generate the call twitter card. In the twitter validation page When you try to validate the previous address, you will return the following message:
ERROR: The page could not be retrieved because the search engine cannot resolve the address.
However, when you enter the CDN endpoint address (
https://EXAMPLE.azureedge.net) in the same validator, then everything is fine and Twitter can read the content of the website. Also, the debugger to share on Facebook does not complain.
Below you can see dark
dig departure for
www.EXAMPLE.io. 60 IN CNAME EXAMPLE.azureedge.net. EXAMPLE.azureedge.net. 1799 IN CNAME EXAMPLE.afd.azureedge.net. EXAMPLE.afd.azureedge.net. 299 IN CNAME afd.t-XXXX.t-msedge.net. afd.t-XXXX.t-msedge.net. 200 IN CNAME t-XXXX.t-msedge.net. t-XXXX.t-msedge.net. 43 IN CNAME XXXXXXXXXXXXX.ctrl.t-XXXX.t-msedge.net. XXXXXXXXXXXXX.ctrl.t-XXXX.t-msedge.net. 223 IN CNAME standard.t-XXXX.t-msedge.net. standard.t-XXXX.t-msedge.net. 236 IN A 188.8.131.52
What can cause the problem and how can I solve it?