Romeo Zwart
Based in Amsterdam (NL)
9
Articles
15
Likes on articles
Based in Amsterdam (NL)
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.
RIPE NCC Technical Services 2017 - Part Three: Focus on Tools and Research
Please find below the third part of our technical services update. This time we're focusing on our research activities and a number of tools we are developing.
RIPE NCC Technical Services 2017 - Part One: Focus on RIPE Atlas
In 2013 and 2015 we provided high-level reports on the status of our plans for our technical services and tools. It is time for an update. In this first article we will focus on RIPE Atlas.
An Updated DNS Monitoring Service
Since 2003, the RIPE NCC’s DNS Monitoring Service (DNSMON), has been providing a comprehensive, objective, and up-to-date overview on the quality of the service offered by TLD and other DNS operators. Due to technical advancements and in line with our aim to provide consolidated services, we are in…
Conclusions Drawn from Reverse DNS Event
On Wednesday 13 June 2012, an unknown error caused the removal of several zone files from the configuration of our reverse DNS provisioning system. Following up from the initial report published on RIPE Labs, we further analysed what caused the incident and implemented a number of procedures to dec…
Showing 5 article(s)
Hi Adrian, Thanks for this feedback. We are following up with you out-of-band to investigate this further. Romeo
“Hi Anand, it's really interesting. I am curious how you decided the location. It seems the ~45% of the request are served from the servers in London. Best, Danilo”
Hi Danilo, The location of this new, experimental, node was not chosen for any specific reason. It is an experiment and as such could have been done in other locations as well. The location of the other service clusters is mostly 'historical'. Amsterdam and London where the first two locations where K-root started, so many many years ago it was a relatively simple next step to add a second DNS cluster to those locations. The Stockholm node was added some time later as part of a broader effort to add more resilience to RIPE NCC's services. Romeo
“Looking forward for the experiment's results. Where do I find that chart in ripestats? Thank you”
Hi Besmir, As mentioned above, we will have more details later. The chart above is currently not publicly available.
“good move! but how about some nodes outside of europe? folk need to resolve reverses all over the internet.”
Hi Randy, If this experiment works out as expected, we will be open to add locations globally, much like we do with K-root. This is in fact one of the reasons why we want to take this approach, because it will allow us to improve our reachability in other regions quite easily.
Showing 4 comment(s)