[apologies for duplicates]
Dear colleagues,
The RIPE NCC experienced an increased query load on K-root and other
root name servers. Please find some analysis and graphs on RIPE Labs
describing this increase.
http://labs.ripe.net/Members/wnagele/increased-query-load-on-root-name-serv…
Please note that we did not see any noticeable degradation of any
Internet services caused by this.
Kind Regards,
Mirjam Kuehne
RIPE NCC
Hello,
IPv6 World Day is tomorrow!
I'm at the ENOG meeting in Moscow, which has a pretty common hotel
Internet setup - a web redirect on first connect and then some magic
somewhere records your information so you get out to the Internet
more-or-less directly from then on.
Someone at the meeting was kind enough to set up IPv6 service here.
Yesterday it seemed a bit bumpy, but today it is working nicely.
However, the network has a somewhat broken DNS resolver, which is also
sadly pretty common at hotels. It seems to have problems answering
normal IPv4 address queries (A records), but mostly works for that. It
does not handle IPv6 address queries (AAAA records) at all. :(
I tried running a resolver on my laptop, but the hotel network restricts
DNS UDP packets to a maximum of 512 bytes. Even worse, it truncates
larger answers to that size, and does not set the truncate bit. This
confuses BIND mightily, as you would expect, since it is basically
getting corrupted packets. Plus it blocks DNS TCP completely. Suffice it
to say IPv4 is damaged here.
A quick Google reveals that OpenDNS has IPv6 servers, which allows me to
use the IPv6 transit, which is free of nonsensical tampering:
http://warrenkwok.blogspot.com/2011/05/opendns-offers-ipv6-resolvers.html
The IPv6 eyechart is now a sea of green! I'm ready for tomorrow. Are
you? :)
--
Shane
