RIPE NCC DNS Update
10
RIPE NCC DNS Update Anand Buddhdev RIPE NCC
description
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 - PowerPoint PPT Presentation
Transcript of RIPE NCC DNS Update
RIPE NCC DNS UpdateAnand BuddhdevRIPE NCC
Presenter Name, Date 2
The GII Team
Presenter Name, Date
Our Services• DNS (K-root, authoritative DNS, secondary
DNS, ENUM, AS112)• DNSMON• Routing information service (RIS)• RIPE Atlas anchors• RIPE Atlas back-ends
3
Presenter Name, Date
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 20144
Presenter Name, Date
Authoritative DNS Instances
5
Presenter Name, Date
Authoritative DNS• Improvements to provisioning system
– Multi-master– Resiliency against hardware or software failure
• Third instance by the end of 2013
6
Presenter Name, Date
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?
7
Presenter Name, Date
ENUM (e164.arpa)• 52 delegations (no change since RIPE 66)• 6 secure delegations
8
Presenter Name, Date
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
9
Questions?
