- dns-wg - mailman.ripe.net

IPv6 reverse DNS meeting at last IETF
by David Kessens 08 Jan '03

08 Jan '03

Hi, I would like to share with you the results of a private discussion that started at a meeting at the last IETF regarding IPv6 reverse delegation issues. The group of people was an ad-hoc group which is worried that the process for moving to ip6.arpa is stagnating. People involved in the discussion were: Kurt Erik Lindqvist David Kessens Johan Ihren Andrei Robachevsky Patrik Faltstrom Jim Reid The topic of the meeting was IPv6 reverse DNS. We agreed on the following: - the move to ip6.arpa is not on track - it's probably best that we start to give attention to this problem in the DNS wg to avoid any duplication in efforts. (BTW this also means that the chairs of the ipv6 wg and DNS wg need a meeting schedule that will allow IPv6 wg participants to attend the DNS wg - we, Jim Reid & David Kessens, have already made this very clear to the RIPE NCC). - Andrei made it clear that the RIPE NCC wants to move forward with a pragmatic approach - we should stop making further delegations in ip6.int (in so far that this is within our powers, at the minimum we can recommend this) - we should make it possible that 3ffe address holders can start getting reverse delegations in ip6.arpa. This is important because it will allow software coders/vendors to do look ups in ip6.arpa only instead of doing kludges by looking in both or in the wrong one (ip6.int) we think this is important to get started as soon as possible since software tends to stay alive longer than desirable Andrei/RIPE NCC was going to ask IAB and/or other powers that be to get this moving. We as a community should help if necessary by a supporting statement. (Andrei already sent his request and is working on a proposal for implementation) - 6to4 reverse delegation We discussed this topic briefly as a lesser priority item. As 6to4 is a transition mechanism for networks that can not get native access to v6, we concluded that reverse delegation might not be that important for the 6to4 addresses. This is clearly a point for more discussion for the DNS wg. Obviously, this is just the opinion of a small group - your comments are welcome! Please follow up to the dns-wg list only (unless you don't agree on moving this topic to the dns-wg in the first place :-)). Thanks, David K. ---

6 7

ANNOUNCEMENT: DNSSEC TRAINING COURSES
by RIPE NCC Training 20 Dec '02

20 Dec '02

Dear colleagues, [apologies for duplicate postings] As a new service to its members the RIPE NCC offers the DNSSEC training courses. The main objective of the DNSSEC training course is to provide LIRs with sufficient background to be able to deploy DNSSEC in their own organisation as soon as the protocol is standardised. This course also explains the specific procedures set up by the RIPE NCC to to secure the in-addr.arpa zone. The Domain Name System (DNS) is one of the main parts of the Internet infrastructure. At the moment DNS lacks a mechanism to establish the authenticity and integrity of the data it provides. DNSSEC is a set of extensions to provide this end-to-end authenticity and integrity. It is currently being developed within the IETF dnsnext working group. The protocol is about to be finalised and the code implementing the protocol is available in alpha releases. The DNSSEC course consists of two parts: an "Introduction to DNSSEC" and a "real life demonstration" . The "Introduction to DNSSEC" will cover: - DNS security threats - DNSSEC security mechanisms - DNSSEC server protection - DNSSEC data protection - Delegation issues - Key management issues - Current developments Examples are based on the BIND name server. Please note that the DNSSEC is an advanced course, it will: - NOT teach the basics of DNS. - NOT describe how to receive Internet resources from the RIPE NCC nor how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network & system operators, engineers, etc. This course is not intended for administrative or management staff (e.g. hostmasters). It is assumed that all attendees are familiar with common DNS terminology, have a practical knowledge in operating DNS servers and are interested in learning the concepts and mechanisms that DNSSEC offers. The DNSSEC course is conducted in the English language and is free of charge, since it is covered by the membership contribution. More information about the DNSSEC training course can be found at: http://www.ripe.net/training/dnssec/ REGISTRATION: You can register for a course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this email and replying to <training(a)ripe.net> In order to register for a DNSSEC course you must be an employee of an LIR and either : - be an LIR contact - be confirmed by an LIR contact. LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the "DNSSEC Training Course" will not be an authorative contact persons for their LIR, therefore will be refused by the course registration "robot". In order to be admited to the course, confirmation email need to be send to <training(a)ripe.net>. Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, The RIPE NCC Training Team COURSE DATES AND VENUES ======================== Date: Saturday 1st February 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands AND: Date: Monday 24th February 2003 Time: 0900 - 1700 Location: Frankfurt, Germany AND: Date: Thursday 27th March 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The Course you plan to attend (date and location) # COURSE [ ] %END

2 1

RIPE NCC's DNS server available in IPv6
by Daniel Diaz 09 Dec '02

09 Dec '02

Dear all, We are glad to announce that since November 29, RIPE NCC's DNS service (ns.ripe.net) is also available in IPv6. This was an action on RIPE NCC for RIPE 43 and it is now accomplished. ns.ripe.net internet address = 193.0.0.193 ns.ripe.net IPv6 address = 2001:610:240:0:193::193 Best regards. -- Daniel.Diaz Operations Manager RIPE NCC

3 2

Re: RIPE NCC's DNS server available in IPv6
by Daniel.Diaz 03 Dec '02

03 Dec '02

Dear Carlos, et al, (Apologies for duplicates). Carlos Friacas <cfriacas(a)fccn.pt> writes: * Hello, * * I have a question about this, as pointed out by one of my colleagues here: * * As the SOA record for ripe.net., the glue record for ns.ripe.net. on * <whatever>.gtld-servers.net is 193.0.0.193, right? * Shouldnt they have also an AAAA record for ns.ripe.net on the net. zone? * Is this scheduled/possible/requestable/desirable??? * Indeed having this IN AAAA record included in the parent zone for ripe.net. would be the most desirable. So far I ignore though if .net nameservers are V6 ready or not. We definitively will look forward getting this record included in our parent zone etc... still the root-zone is not V6 ready yet, so the tree can not be completed anyway. With best regards. -- Daniel.Diaz Operations Manager RIPE NCC

4 3

Re: RIPE NCC's DNS server available in IPv6
by Daniel.Diaz 03 Dec '02

03 Dec '02

apologies for duplicates. "Daniel.Diaz" <ddiaz(a)ripe.net> writes: * Indeed having this IN AAAA record included in the parent zone for ripe.net ^^^^^^^^^^ |||||||||| Sorry... this was meant to be 'ns.ripe.net' * would be the most desirable. So far I ignore though if .net nameservers are V6 * ready or not. * We definitively will look forward getting this record included in our * parent zone etc... still the root-zone is not V6 ready yet, so the tree can not * be completed anyway. -- Daniel.Diaz

1 0

Fw: ?:? .NAME...Still in Proof-of-Concept Phase ?
by Jim Fleming 27 Nov '02

27 Nov '02

NSpace : Name.Space : 209.48.2.11 VueDig Results : Answer = 2 : Authority = 0 : Additional = 2. NAME. 2D IN NS NS.ICANN.ORG. NAME. 2D IN NS NS.RIPE.NET. Sent: Wednesday, November 27, 2002 9:18 AM Subject: ?:? .NAME...Still in Proof-of-Concept Phase ? > http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt > ?:? .NAME > ==== > > http://www.icann.org/minutes/report-gnr-whois-26nov02.htm > > http://root-dns.org/vuedig/vuedig_tld.php?record=NS&tld=NAME&submit=Submit > Analysis : Top Level Domain NAME exists. > > > Jim Fleming > 128-bit DNS is closer than you think... > IPv16...COM...NET...AM...NZ...AE...FM...NR...SZ...AC...DE...FI...JM...NO...PR...ST...UZ > http://ipv8.dyndns.tv > http://ipv8.dyns.cx > http://ipv8.no-ip.com > http://ipv8.no-ip.biz > http://ipv8.no-ip.info > http://ipv8.myip.us > http://ipv8.dyn.ee > >

1 0

"the European Commission to run the proposed .EU TLD registry." ?
by Jim Fleming 20 Nov '02

20 Nov '02

http://www.dnso.org/clubpublic/registrars/Arc01/msg03617.html From: "Paul M. Kane" <Paul.Kane(a)REACTO.com> "the European Commission to run the proposed .EU TLD registry." === http://root-dns.org/vuedig/vuedig_tld.php?record=NS&tld=eu&submit=Submit Analysis : Top Level Domain EU exists. ORSC : Open Root Server Confederation : 199.166.24.1 VueDig Results : Answer = 2 : Authority = 0 : Additional = 0. eu. 1D IN NS uk.universalroot.com. eu. 1D IN NS us.universalroot.com. Jim Fleming 128-bit DNS is closer than you think... IPv16...NET...COM...AM...NZ...AE...FM...NR...SZ...AC...DE...FI...JM...NO...PR...ST...UZ http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee http://ipv8.community.net.au

1 0

Correction...NL.NZ...??Re: .UK ?...3:71 GB (UNITED-KINGDOM)
by Jim Fleming 20 Nov '02

20 Nov '02

Will .NL be moving under .NZ ?.....NL.AM....or NL.NR...?..or NL.NO ? ...or NL.EU ? Where will .UK end up ? IPv16...NET...COM AM...NZ AE...FM...NR...SZ AC...DE...FI...JM...NO...PR...ST...UZ ----- Original Message ----- From: "Jim Fleming" <JimFleming(a)ameritech.net> To: "Pim van Pelt" <pim(a)ipng.nl> Cc: "RIPE DNS WG" <dns-wg(a)ripe.net> Sent: Wednesday, November 20, 2002 3:06 PM Subject: Re: .UK ?...3:71 GB (UNITED-KINGDOM) > ----- Original Message ----- > From: "Pim van Pelt" <pim(a)ipng.nl> > > ---------- - - - - -+- - - - - ---------- > > Pim van Pelt Email: pim(a)ipng.nl > > http://www.ipng.nl/ IPv6 Deployment > > ----------------------------------------------- > > Will .NL be moving under .AM ?.....NL.AM....or NL.NR...?..or NL.NO ? > > Where will .UK end up ? > > IPv16...NET...COM > AM...NZ > AE...FM...NR...SZ > AC...DE...FI...JM...NO...PR...ST...UZ > >

1 0

.UK ?...3:71 GB (UNITED-KINGDOM)
by Jim Fleming 20 Nov '02

20 Nov '02

http://www.arin.net/library/internet_info/RIPEcountries.htm UNITED KINGDOM GB GBR RIPE ==== 3:71 GB (UNITED-KINGDOM) Jim Fleming 128-bit DNS is closer than you think... IPv16...NET...COM...AM...NZ...AE...FM...NR...SZ...AC...DE...FI...JM...NO...PR...ST...UZ http://ipv8.dyndns.tv http://ipv8.dyns.cx http://ipv8.no-ip.com http://ipv8.no-ip.biz http://ipv8.no-ip.info http://ipv8.myip.us http://ipv8.dyn.ee http://ipv8.community.net.au

2 2

Correction
by RIPE NCC WebMaster 12 Nov '02

12 Nov '02

Dear Colleagues, The draft document: "DRAFT: Distributing K-Root Service by Anycast Routing of 193.0.14.129" is available from: http://www.ripe.net/ripe/draft-documents/k-root-anycasting.html Apologies for the incorrect URL earlier. Regards Jeroen Bet RIPE NCC WEBMASTER ==================

1 0