Collecting Microsoft Issues with IPV6 only 20221107

Cloud management gateway

Visual Studio: All those services have no AAAA records

Github.com

linkedin.com

Linkedin is proud to be IPv6 enables since 2016 ( IPv6 at LinkedIn Part I, IPv6 Inside LinkedIn Part II, IPv6 Inside LinkedIn Part III: The Elephant in the Room, LinkedIn Passes IPv6 Milestone) but still there is a Probelm. Linkedin used Microsoft CDN which Nameservers donot yet support IPv6.

www.linkedin.com. 300 IN CNAME www-linkedin-com.l-0005.l-msedge.net.
www-linkedin-com.l-0005.l-msedge.net. 240 IN CNAME l-0005.l-msedge.net.
l-0005.l-msedge.net. 240 IN AAAA 2620:1ec:21::14

l-msedge.net. 84113 IN NS ns1.l-msedge.net.
l-msedge.net. 84113 IN NS ns2.l-msedge.net.
Both anycast NS donot have a AAAA record.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.