This is the second part in a series of articles looking at the use of DNS servers in Iran. For the second part I will continue measuring performance and reachability for two more sets of DNS resolvers: TIC and Verisign.
While most Internet users are not aware of the importance of DNS resolution in their overall web browsing experience, they often complain about shortage of bandwidth when experiencing sluggish Internet connectivity. It is no surprise that most of the service providers also ignore this fact by redirecting their customer DNS traffic to public DNS servers.
RIPE Atlas has been in operation for more than five years now, and its network of probes and users has grown tremendously in that time. We’ve also added anchors, sponsors and ambassadors to the system, developed a huge array of new tools, visualisations and features, and RIPE Atlas data is now being used by network operators, engineers and researchers around the world. As a result, we thought it was time to revamp the RIPE Atlas website, which hadn’t changed much over the past five years despite all the changes to RIPE Atlas itself. Get an overview of some of the biggest changes and new features - then check out the new site, which launches today!
In this report we provide some more details about the incidents of 30 November and 1 December 2015, as seen from the K-root environment. We also share some of the lessons we took away from this event.
I was at FOSDEM 2016 last weekend, and wrote up a few of my observations around DNS there. Enjoy!
RIPE Atlas had another successful year in 2015, thanks in large part to all our users, hosts, sponsors, ambassadors and other community members. Here we take a look back at some of the achievements we reached together, the new features we implemented, key facts and figures - and offer a sneak peek of what you can expect in 2016.
One of the more difficult design exercises in packet-switched network architectures is that of the design of packet fragmentation. In this article, I’d like to examine IP packet fragmentation in detail and look at the design choices made by IP version 4, and then compare that with the design choices made by IP version 6.
RIPE Atlas collects a lot of measurements. But how much of the Internet are we actually measuring? We had a sense that with a limited amount of extra load on the system, we could dramatically increase the number of router IPs seen on a given day in RIPE Atlas - and that means measuring more of the Internet.
Wouldn’t it be nice if turning on IPv6 really was ‘press one button and the rest is magic’ easy?
A little while ago, we asked what you thought about the idea of conducting WiFi measurements in RIPE Atlas. After some consideration and community feedback, we now want to propose a way to implement this feature in RIPE Atlas and clarify exactly how these measurements will benefit the RIPE Atlas community.