Dominik, Follow the records for www.linkedin.com. LinkedIn uses GLB DNS resolution off of www and since glb-eu isn't working for you, that means they probably are not using that right now.
-Grant On Sat, Oct 4, 2014 at 12:50 PM, Dominik Bay <[email protected]> wrote: > Hi, > > I'm seeing this strange issue where LinkedIn is not working properly via > IPv6. > At least 2620:109:c007:102::5be1:f881 is not working in several eyeball > networks in Germany, 2620:109:c006:102::6cae:281 is working, but not > returned often via DNS lookup. > Also the DNS RR entries change often so I can not really pinpoint what > customer got which IP address back that didn't work. > > Is this a known issue? I'm seeing it for about 2-3 days already. > > Best, > Dominik > > > > $ host www.linkedin.com > www.linkedin.com is an alias for pop-ela4-alpha.www.linkedin.com. > pop-ela4-alpha.www.linkedin.com has address 199.101.163.129 > pop-ela4-alpha.www.linkedin.com has IPv6 address > 2620:109:c00d:100::c765:a381 > > $ telnet www.linkedin.com 80 > Trying 2620:109:c006:102::6cae:281... > Connected to www.linkedin.com. > Escape character is '^]'. > ^] > telnet> quit > Connection closed. > > > $ host glb-eu.www.linkedin.com > glb-eu.www.linkedin.com is an alias for pop-idb2-alpha.www.linkedin.com. > pop-idb2-alpha.www.linkedin.com has address 91.225.248.129 > pop-idb2-alpha.www.linkedin.com has IPv6 address > 2620:109:c007:102::5be1:f881 > > $ telnet glb-eu.www.linkedin.com 80 > Trying 2620:109:c007:102::5be1:f881... > Trying 91.225.248.129... > Connected to glb-eu.www.linkedin.com. > Escape character is '^]'. > ^] > telnet> quit > Connection closed. >
