I tested accessing the CDN by another domain and DNS provider. It doesn’t fetch the image from another domain with another DNS provider with CNAME to the CDN. So, I’m %100 percent sure it’s not an issue with DNS provider.
I contacted Microsoft support again but they checked again and told:
“The issue seems to be a problem with Twitter on how the DNS resolution is being done. And also we see that the expected result has been achieved when browsed in any other browsers.”
I just did several DNS tests by several tools and there the DNS resolution works fine by them. I just found that Twitter uses Netty for DNS resolution and the error you sent me “status:UnresolvedAddress” comes from Netty.
It seems there is an issue (or conflict with our DNS settings) in your DNS resolution software implemented with Netty. Mind you report it to your development team to help or find a solution for it?
Thanks for your support,