- dns-wg - mailman.ripe.net

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

DNS Maintenance on ns.ripe.net, 19 Sept
by Sjoerd Oostdijck 17 Sep '07

17 Sep '07

[Apologies for duplicate e-mails.] Dear Colleagues, On Wednesday, 19 September 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

Leaving the RIPE NCC
by Brett Carr 14 Sep '07

14 Sep '07

I will be moving back to the UK and hence leaving the RIPE NCC on September the 20th. I would like to thank all WG members for the help and support over the last 3 years. Rest assured DNS services at the NCC are in the safe hands of Anand and Sjoerd, and Andrei will take over the running of the team until a replacement has been hired. As always queries and problems can be sent to dns-help(a)ripe.net and will be dealt with swiftly. Thanks Brett -- Brett Carr RIPE Network Coordination Centre Manager -- DNS Services Group Singel 258 Amsterdam NL GPG Key fingerprint = F20D B2A7 C91D E370 44CF F244 B6A1 EF48 E743 F7D8

1 0

DNS Maintenance on ns-tld.ripe.net, 12 Sept
by Sjoerd Oostdijck 06 Sep '07

06 Sep '07

[Apologies for duplicate e-mails.] Dear Colleagues, On Wednesday, 12 September 2007, we will update our DNS server ns-tld.ripe.net between 17:00 and 17:15 (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

4 3