On 19 May 2013 00:32, Noel Butler <noel.butler@ausics.net> wrote:
On Sat, 2013-05-18 at 22:55 -0700, Constantine A. Murenin wrote:
People talk about publishers not turning on IPv6 for their domains, since there are misconfigured clients; I'd say IPv6 clients face a bigger problem, in the face of so many misconfigured servers.
And fb.me is still down, BTW.
8 2620:0:1cff:dead:beef::12b5 286.407 ms 2620:0:1cff:dead:beef::12d1 289.605 ms 2620:0:1cff:dead:beef::105f 289.441 ms
9 * * * 10 * * *
kinda the right addressing at least not that I care, given I dont facebook as i value my privacy
I use twitter, and people use fb.me links on twitter, which didn't work. Heh, finally someone must have noticed, and instead of fixing it for IPv6, they've just removed the AAAA record: li16x-xxx:~# telnet fb.me http Trying 173.252.110.27... Connected to fb.me. Escape character is '^]'. ^CConnection closed by foreign host. li16x-xxx:~# telnet -6 fb.me http telnet: could not resolve fb.me/http: Name or service not known But it's still amusing that it's been down for so long. I wonder how many hours (or possibly even days) it's been down for. :-) C.