Bruce Campbell. ISOC Workshopl, 21 June 2004, Amsterdam. RIPE NCC DNS Architecture (for ccTLD secondarying) Nameserver Planning for.

Slides:

Advertisements

Similar presentations

ICANN Security and Stability Advisory Committee ICANN Meetings Shanghai October 30, 2002.

Advertisements

Sergei Komarov. DNS  Mechanism for IP hostname resolution  Globally distributed database  Hierarchical structure  Comprised of three components.

Supercharging PlanetLab : a high performance, Multi-Application, Overlay Network Platform Written by Jon Turner and 11 fellows. Presented by Benjamin Chervet.

1 Routing Worm: A Fast, Selective Attack Worm based on IP Address Information Cliff C. Zou, Don Towsley, Weibo Gong, Songlin Cai Univ. Massachusetts, Amherst.

IANA Status Update ARIN XXVI meeting, Atlanta Barbara Roseman October 2010.

DNS Issues Within Native IPv6 GEANT GEANT-TF, Amsterdam, 06/06/2003.

A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E APNIC Open Address Policy Meeting What is Reverse DNS October 26th, Brisbane Bruce.

RIPE NCC Cooperation Update Paul Rendek Head of External Relations and Communications.

Establishing ccTLDs in Africa - Overcoming The Challenges Michuki Mwangi President AfTLD AfTLD Meeting 7th, April 2008 Johannesburg, South-Africa.

Introducing IANA Root Management A presentation to APTLD-ccTLD workshop in the Pacific Save Vocea ICANN’s regional rep. – Australasia/Pacific Noumea, April.

UAEnic مركز الإمارات لمعلومات شبكة الإنترنت Presented By: Sultan Al Shamsi GCC ccTLD Working Group Meeting 7 th March 2004 Riyadh, KSA.

CcNSO Finance Working Group: Survey on ICANN Contributions and Services Byron Holland March 11,

IANA Department Activities, RIPE 66, Dublin, Ireland May 2013 Elise Gerich.

1 Mirjam KühneINET MEA, Cairo, May 2004 Welcome to INET MEA Cairo, Egypt 8 May 2005 Mirjam Kühne, ISOC.

Overview of implementations openBGP (and openOSPF) –Active development Zebra –Commercialized Quagga –Active development XORP –Hot Gated –Dead/commercialized.

Introducing IANA Root Management ccTLD workshop, Guyana 2007 John Crain Internet Corporation for Assigned Names and Numbers.

An overview of IP addressing history and policy issues Leo Vegoda Number Resources Manager, IANA.

Mirjam Kühne 1 RIPE 33, May 1999 Introduction to the RIPE NCC presented by Mirjam Kühne.

11 November 2001 Marina del Rey GAC meeting Vulnerabilities in the Internet Jaap Akkerhuis.

Address Policy SIG, APNIC Policy meeting, February 27th, 2003 (1) IPv6 Policy in action Feedback from other RIR communities David Kessens Chairperson RIPE.

Solving Quadratic Equations by Factoring. Solution by factoring Example 1 Find the roots of each quadratic by factoring. factoring a) x² − 3x + 2 b) x².

Mirjam Kühne 1 EC, Oct Policy Development in RIPE & the RIPE NCC Mirjam Kühne RIPE NCC.

* Agenda  What is the DNS ?  Poisoning the cache  Short term solution  Long term solution.

Patrik Fältström. ITU Tutorial Workshop on ENUM. Feb 8, 2002, Geneva Explanation of ENUM (RFC 2916) Patrik Fältström Area Director, Applications Area,

Management of Internet Resources ITU Workshop on Developing a Policy and Regulatory Framework for Developing Economies of the Pacific 1 December 2003 Suva,

Internet Protocol Addresses What are they like and how are the managed? Paul Wilson APNIC.

UNDERSTANDING YOUR OPTIONS FOR CLIENT-SIDE DEVELOPMENT IN OFFICE 365 Mark Rackley

Internetworking Lecture 10 October 23, Introduction to Internetworking So far, we’ve discussed about how a single network functions. Internetworking.

Ch 6: DNSSEC and Beyond Updated DNSSEC Objectives of DNSSEC Data origin authentication – Assurance that the requested data came from the genuine.

UAEnic United Arab Emirates Amani Mohammed Bin Sewaif Zain Al Abdeen Baig November 2007.

Mirjam KuehneRIPE Meeting # 31 RIPE ncc Internet Administration and the RIPE NCC Daniel Karrenberg.

Zone Transfers Summary of CENTR Position Kim Davies ICANN Shanghai 27 October 2002.

INTERNET ADDRESSING Today’s topics:  What are Internet addresses?  Why do we need them?  How are they used?

APNIC DNSSEC deployment considerations APNIC 23, Bali George Michaelson R&D Officer APNIC.

Copyright (c) 2002 Japan Network Information Center Proposal for IPv6 Policy for Essential Infrastructure in the AP region Izumi Okutani IP Address Section.

RIPE Network Coordination Centre APRICOT Feb Mirjam Kühne..illuminating new ideas and tools from the community for the community.

APTLD MEETING Manila 23 – 24 February ccTLD Role in Its Community RFC 1591 Introduction  Foresaw a few TLDs (edu, com, net, org, gov, etc.) and.

CcTLD Issues AFNOG Accra, Ghana May, 2001 Andrew McLaughlin.

1 DNS Operations SIG Report Joe Abley, ISC APNIC 18 Nadi, Fiji, September 2004.

IANA FUNCTIONS STEWARDSHIP TRANSITION

The IETF World of Standardisation Jon Crowcroft,

Lecture 2: Leaf-Spine and PortLand Networks

High Availability Linux (HA Linux)

Database backed DNS.

Principles of Computer Security

ICANN Meeting, Kuala Lumpur, July 2004

IEPG Minneapolis, March 1999

Academic Talent Search

DNS Session 5 Additional Topics

Infrastructure & Separation of Services

Unit 5: Providing Network Services

Lecture 5: GPU Compute Architecture

ICANN62 GAC Capacity Building

Lecture 5: GPU Compute Architecture for the last time

Christopher Wilkinson Head, GAC Secretariat

Internet Addressing Today’s topics: What are Internet addresses?

ICANN/IANA Update at APNIC 29

A Proposal for IPv4 Essential Infrastructure

Joint IPv6 Forum/IPv6 SIG APNIC 15, Taipei, Taiwan 26 February 2003

Locking down the final /8 Remco van Mook

Infrastructure & Separation of Services

Conficker Mitigation in .at

X by 20 Can you remember how to x by 20? Lets try 25 x 20

Dr. John P. Abraham Professor UTRGV

IPv6 Address Space Management

James Blessing, Sandra Brown,

Presentation transcript:

Bruce Campbell. ISOC Workshopl, 21 June 2004, Amsterdam. RIPE NCC DNS Architecture (for ccTLD secondarying) Nameserver Planning for the long term. Bruce Campbell

Bruce Campbell. ISOC Workshop, 21 June 2004, Amsterdam. Problem Outline Policy of secondarying ccTLDs: –We’ll secondary anyone’s ccTLD. Single name (ns.ripe.net): –Single machine. –Memory footprint issues (lots of large zones). –Can’t renumber as need signoff from far too many parties; individual redelegating for performance (eg.de) takes too long. DNSSEC is scary: –Increases individual zone footprint significantly. –Machine has finite possible memory size.

Bruce Campbell. ISOC Workshop, 21 June 2004, Amsterdam. Solution Shift away from single name (and address): –Still single machine, but lots of IP aliases. –Lots of glue records in root zone. –Can ‘go IPv6’ on a per ccTLD basis, not ‘all or nothing’. No renumbering required when zone grows beyond machine’s capacity. –Can drop in a new machine and remove IP alias on the previous machine at any time without needing editing of the root zone (IANA).

Bruce Campbell. ISOC Workshop, 21 June 2004, Amsterdam. Renaming what to what? Old name: ‘ns.ripe.net’ New name: ‘ns-XX.ripe.net’ –‘XX’ is the ISO3166 country code – ‘ns-af.ripe.net’ –Separate address for each one – eg ‘ ’, ‘ ’ Good chance to talk to IANA –They don’t bite.

Bruce Campbell. ISOC Workshop, 21 June 2004, Amsterdam. Names to delegate to: ns-BI.ripe.net – , 2001:610:240:0:53:cc:12:24 ns-BJ.ripe.net – , 2001:610:240:0:53:cc:12:36 ns-LK.ripe.net – , 2001:610:240:0:53:cc:12:208 ns-NP.ripe.net – , 2001:610:240:0:53:cc:12:154 ns-TH.ripe.net – , 2001:610:240:0:53:cc:12:219 ns-UY.ripe.net – , 2001:610:240:0:53:cc:12:237

Bruce Campbell. ISOC Workshop, 21 June 2004, Amsterdam. Summary and Questions Trying to avoid ‘last minute’ renumbering and possible frustrations. Easy upgrade path for NCC’s hardware as the total size of zones approaches upper memory limit on a single machine. Lets the NCC do maintenance work without interrupting service (IP aliases can be moved between spare machines easily) IPv6 connectivity for your zone with no pain to you.