Thanks for the update Sander. The following seems to have the full info. http://translate.google.com/translate?depth=1&hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=auto&tl=en&u=http://ipv6.br/teredo-sunset-mais-um-passo-na-transicao-para-o-ipv6/
At the same time, i'm thinking out loud... Why would a windows application send an a request to an IPv6 DNS server over native IPv6 in order to find the IPv4 address of a server and get IPv6 over IPv4 connectivity? -- Tassos Sander Steffann wrote on 12/7/2013 02:31: > Hi, > >> Anyone found out what happened with teredo.ipv6.microsoft.com ? >> >> http://translate.google.com/translate?hl=en&sl=de&u=http://www.heise.de/netze/meldung/IPv6-Tunnel-Microsofts-Teredo-Server-nicht-erreichbar-1915972.html&prev=/search%3Fq%3Dteredo%2Bmicrosoft%2Bipv6%26safe%3Doff%26sa%3DX%26biw%3D1303%26bih%3D803%26tbs%3Dqdr:w >> >> Since yesterday we have quite an increase of NXDOMAIN in relevant dns >> requests. >> >> Has Microsoft made the big step? > Almost :-) This is what is happening now: > >> As an attempt to "measure" the impact of this sunsetting, we would like to >> switch off the service for a few days. Resultant feedback and telemetry will >> help us inform the future of the Teredo service and its default configuration >> on Windows. We intend to conduct this experiment from approximately July 9 >> 0:0:00 UTC, to July 15 0:0:00 UTC. > So it will come back, but it *is* the start of the sunsetting process. > > Cheers, > Sander > > >
