We're getting ready to expand K-root coverage, and we'll soon be inviting interested members of the community to express their interest in hosting their own K-root node. Learn more about how we propose expanding the network, what the requirements are for hosting your own K-root node, and the projected timeline.
Romeo works for the RIPE NCC. He is manager of the Global Information Infrastructure team responsible for RIPE NCC DNS Services (e.g. K-root), Routing Information Services (RIS) and RIPE NCC's Hadoop storage platform, powering RIPEstat and RIPE Atlas.
Pages created by Romeo Zwart
We have redesigned the K-root architecture for our hosted nodes, formerly known as K-root local instances. System architecture and network setup have been simplified a lot. This will reduce our management effort for K-root and reduce costs for K-root hosts.
The RIPE NCC announced a new version of DNSMON, available for testing by the public, in March 2014. We are now planning the removal of the old DNSMON.
This report is a follow up to an earlier article, in which we detailed our investigations into the use of virtualisation technology as a suitable means to provide other services via the RIPE Atlas anchor hardware, beyond its primary anchor function.
This article describes the main results of a research project undertaken by Luigi Corsello. During this project Luigi looked at possibilities to use virtualisation technology to expand RIPE Atlas anchors to provide additional services.