After the RIPE NCC implemented a system that checks for lame DNS servers in the part of the DNS tree the RIPE NCC maintains I was curious to find out how big a problem DNS lameness really is. I wrote a tool and presented it at the DNS WG during RIPE 59 in Lisbon.
While walking around the hallways at RIPE59, a couple of people asked me how the movies were made, what tools did I use and such. So here's a short summary on what I did to produce these movies.
The current version (v0.1) knows only about IPv4 address space. We went for the most difficult part first. ASNs and IPv6 address space will follow (please note the follow-up articles below describing additional functionality about the Resource Explainer).
INRDB is a non-conventional database hosting many different, number resource related data sets.
Let us show you the RIR assigned and allocated IPv4 space, and some indication on how that's routed in the Internet. Get out the popcorn! Satisfaction guaranteed!
Based in Western Europe, NL&DE mostly
>>>>>>>>>>>> https://www.ripe.net/about-us/press-centre/publications/speakers/daniel-karrenberg <<<<<<<<<<<< Ample information about his past sins can be found using your favourite search engine. Following are a few additional keywords you might use, arranged by decade: 1980s: GUUG EUUG EUnet unido mcvax cwi RARE iepg RIPE; 1990s: RIPE+NCC rir iana postel terena ebone centr k.root-servers.net; 2000s: dnsmon nsd ris internet+society rssac; 2010s: ripe+labs ripestat ripe+atlas
We look at the consumption rate of 16-bit ASNs and try to make an educated guess on how long they would last if the current allocation rules would be extended.