1 / 10

RIPE NCC DNS Update

RIPE NCC DNS Update. Anand Buddhdev RIPE NCC. The GII Team. Our Services. DNS (K-root, authoritative DNS, secondary DNS, ENUM, AS112) DNSMON Routing information service (RIS) RIPE Atlas anchors RIPE Atlas back-ends. K-root. Service stable with 17 instances Major OS upgrade in progress

kelton
Download Presentation

RIPE NCC DNS Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RIPE NCC DNS Update • Anand Buddhdev • RIPE NCC

  2. The GII Team

  3. Our Services • DNS (K-root, authoritative DNS, secondary DNS, ENUM, AS112) • DNSMON • Routing information service (RIS) • RIPE Atlas anchors • RIPE Atlas back-ends

  4. K-root • Service stable with 17 instances • Major OS upgrade in progress • Better configuration management and deployment with Ansible • Some sites undergoing hardware replacement • No expansion for the time being • Expansion is planned for 2015 • Watch for announcements in 2014

  5. Authoritative DNS Instances

  6. Authoritative DNS • Improvements to provisioning system • Multi-master • Resiliency against hardware or software failure • Third instance by the end of 2013

  7. ccTLD Secondary DNS • 71 ccTLDs (26 in RIPE NCC service region) • 240 zones • Second-level domains • Internationalized domain names • Best-effort – no service-level agreements • We prefer an open and transparent approach • Who qualifies for this RIPE NCC service? • What criteria should the RIPE NCC apply when offering or rejecting this service to a ccTLD?

  8. ENUM (e164.arpa) • 52 delegations (no change since RIPE 66) • 6 secure delegations

  9. DNSMON • Atlas-based interface in development • Measurements from RIPE Atlas anchors and probes • Testing in Q4 2013 • Release in Q1 2014 • TTM-based DNSMON deprecation • Will be unsupported after 2013 • Raw data from RIPE Atlas • Adapt your scripts

  10. Questions?

More Related