- dns-wg - mailman.ripe.net

Announcement DNS for LIRs Training Courses
by RIPE NCC Training Services 12 Nov '07

12 Nov '07

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC Training Services Department invites you to register for one of our upcoming DNS for LIRs Training Courses: Date: Tuesday 29 January 2008 Time: 09:00-17:00 Location: London, United Kingdom And Date: Wednesday 20 February 2008 Time: 09:00-17:00 Location: Vienna, Austria Hosted by: Nic.at: http://www.nic.at/ The main objective of the DNS for LIRs Training Course is to provide LIRs with information about the different DNS related services the RIPE NCC has available for them. It covers reverse DNS procedures and checks, as well as giving information about DNS Monitoring (DNSMON), K-Root and anycasting. The course also covers DNSSEC and the specific procedures set up by the RIPE NCC to secure the in-addr.arpa zones. Please note that the DNS for LIRs course focuses on DNS services and procedures related to being an LIR. The course does: - NOT teach the basics of DNS - NOT describe how to receive Internet resources from the RIPE NCC - NOT describe fully how to operate a Local Internet Registry (LIR) The course is intended for technical staff of LIRs. It is assumed that all attendees are familiar with common DNS terminology and have a practical knowledge of operating DNS servers. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. You can find more information about the course at: http://www.ripe.net/training/dns REGISTRATION: ============ To register for this course, please use the LIR Portal or complete the registration via our website on: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

v6 DNS testbed for TLD?
by Ruri Hiromi 26 Oct '07

26 Oct '07

Hello, I just join this mailing-list and I am very new to the DNS- WG@ARIN. As I said in my presentation "what can I do for dns grue record?", If we share some test environment/simulator for conformance and stable operation for TLD name servers, will it go a step forward? Or does ARIN community already have such testbed? Regards, ------------------------------- Ruri Hiromi hiromi(a)inetcore.com

1 1

Advisory - L.ROOT-SERVERS.NET changing to 199.7.83.42 on 2007-11-01
by Kim Davies 24 Oct '07

24 Oct '07

Colleagues, This is advance notice that there is a scheduled change to the IP address for one of the authorities listed for the DNS root zone. The change is to L.ROOT-SERVERS.NET, which is administered by ICANN. The new IPv4 address for this authority is: 199.7.83.42 This change is anticipated to be implemented in the root zone on 1 November 2007, however the new address is operational now. It will replace the previous IP address of 198.32.64.12. We encourage operators of DNS infrastructure to update any references to the old IP address, and replace it with the new address. In particular, many DNS resolvers have a DNS root "hints" file. This should be updated with the new IP address. New hints files will be available at the following URLs once the change has been formally executed: ftp://rs.internic.net/domain/db.cache ftp://rs.internic.net/domain/named.cache ftp://rs.internic.net/domain/named.root ftp://ftp.internic.net/domain/db.cache ftp://ftp.internic.net/domain/named.cache ftp://ftp.internic.net/domain/named.root It is expected that the old address will continue to work for at least six months after the transition, but will ultimately be retired from service. With kindest regards, Kim Davies Internet Assigned Numbers Authority

1 0

Finally: first draft for RIPE203bis
by Peter Koch 24 Oct '07

24 Oct '07

Dear DNS WG, there is no real good excuse I could come up with for the long delay, so I won't try. With apologies, please find attached the ASCII version of a first draft document of an update to RIPE-203 "Recommended DNS SOA Values" and a diff to the original(*) version. Changes are a new value for the negative TTL, an explicit hint that the recommended values should not be unconditionally enforced and some editorial updates. Feedback welcome, with one early opportunity during this afternoon's WG session. -Peter (*) the "original" version was based on the text version of an Internet-Draft and thus contains some potentially confusing headers and footers. These were edited away before applying the "diff" function. <ftp://ftp.ripe.net/ripe/docs/ripe-203.txt>

1 0

RIPE-55 coming up -- Agenda's items sought
by Jaap Akkerhuis 18 Oct '07

18 Oct '07

Yes, it is that time of the year. In seven weeks we will have another RIPE meeting. We have the usual two slots. Please provide agenda items or suggestions for such items. Mail them to the list or just to the chairs. Let me remind you that only your contributions can make RIPE meetings to a success. jaap

3 2

DNS Migration document
by Jim Reid 18 Oct '07

18 Oct '07

At long last, there is progress on AP49.1. I have revised the document that Fernando presented to the WG. It's attached below. Comments and feedback are welcome. My hope is that the WG does not discuss the document in detail at next week's meeting. There will probably be some revisions needed -- send text! -- so a line-by-line dissection at RIPE55 will not be productive. Though if that's what the WG wants to do.... IMO it would be better if the WG discussed next week what to do with the document. ie Should sections be added or removed, should it be made less implementation-specific and what should happen to the document once the WG is finished reviewing it. In other words, should it be published as a RIPE document or not and what, if anything, needs to be done to get it to that state. These sorts of things would perhaps be a better focus for discussions next week.

2 2

DNS Maintenance on ns.ripe.net, 10 Okt
by Sjoerd Oostdijck 08 Oct '07

08 Oct '07

[Apologies for duplicate e-mails.] Dear Colleagues, On Wednesday, 10 Oktober 2007, we will update our DNS server ns.ripe.net between 17:00 and 18:00 (UTC). During this period, it will not be able to answer DNS queries. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <dns-help(a)ripe.net>. Regards, Sjoerd Oostdijck, DNS Services RIPE NCC

1 0

Deploying DNSSEC in e164.arpa zone
by Andrei Robachevsky 01 Oct '07

01 Oct '07

Dear Colleagues, The RIPE NCC is pleased to announce its plan for the deployment of DNSSEC in the e164.arpa zone (ENUM). This improvement to the operation of the domain was developed and concluded following consultation with the IETF's Internet Architecture Board (IAB). In line with the IAB's instructions, the RIPE NCC has provided technical administration for the e164.arpa zone since 2002. These instructions are documented and are available at: http://www.ripe.net/enum/instructions.html We informed the IAB of our intention to implement DNSSEC in the e164.arpa zone and we received positive feedback and support for the deployment. Details of the correspondence between the RIPE NCC and the IAB can be found at: http://www.iab.org/documents/correspondence/ We will start signing the e164.arpa on 26 November 2007 and support for secure delegations will be provided on 24 March 2008. Further announcements will be posted as these milestones approach. Best regards, Andrei Robachevsky Chief Technical Officer RIPE NCC

6 9

DNS Maintenance on ns-pri.ripe.net, 26 Sept
by Sjoerd Oostdijck 26 Sep '07

26 Sep '07

[Apologies for duplicate e-mails.] Dear Colleagues, On Wednesday, 26 September 2007, we will update our DNS server ns.ripe.net between 17:00 and 18:00 (UTC). During this period, it may not be able to answer DNS queries. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <dns-help(a)ripe.net>. Regards, Sjoerd Oostdijck, DNS Services RIPE NCC

1 0

Last Call: Secondary service on ns.ripe.net for reverse delegations
by Peter Koch 19 Sep '07

19 Sep '07

Dear WG, at the Tallinn meeting, Brett Carr gave a presentation on DNS operations at the RIPE NCC. In his report a proposal regarding the DNS name service for /16 reverse was made. See <http://www.ripe.net/ripe/wg/dns/r54-minutes.html>, item [D] for the minutes and slide 12 of the presentation <http://www.ripe.net/ripe/meetings/ripe-54/presentations/DNS_update.pdf> for details. This resulted in action item 54.1 on the NCC to solicit feedback on the proposal. Brett started a thread on the DNS WG mailing list on May, 14th <http://www.ripe.net/ripe/maillists/archives/dns-wg/2007/msg00107.html> (Message-ID: <4A6256C3-97B5-4415-BC93-9A2978A01A20(a)ripe.net>). Summary: To eliminate an inconsistency between IPv4 and IPv6 policies, where /16 reverse on ns.ripe.net is mandatory for v4 and there's no such policy for v6, three options were given: 1) Make ns.ripe.net mandatory on ipv4 and ipv6 delegations 2) Make ns.ripe.net optional on ipv4 and ipv6 delegations 3) Discontinue the secondary service on ns.ripe.net for new delegations. The NCC's preference was (2). The thread started as mentioned above saw 8 replies until June. Those who expressed an opinion were in favour of going forward with (2). Since the thread hasn't been active for a while, the WG chairs would like to issue a Last Call on this topic. Please take these remarks into consideration: o While cost of service has been mentioned, detailed discussion would be a topic for the NCC Services WG. For now we assume that the cost structure (essentially: no additional cost) will remain unmodified. o When the secondary service is "optional" this should be read in a symmetric way, i.e. not only the /16 maintainer can choose to opt-out, but also the NCC could, on reasonable operational grounds, terminate or not activate support for a particular zone. Now, finally, even though this issue is not subject to the PDP, this is a Last Call until Friday, 31 August 2007, 12:00 UTC Please voice your opinion, the default will be to continue with (2) above. We'd like to ask the NCC to prepare an implementation plan after this date. -Peter Koch [DNS WG co-chair]

3 4