- dns-wg - mailman.ripe.net

More anchors involved in DNSMON measurements
by Robert Kisteleki 16 Jul '14

16 Jul '14

Dear DNSMON users, Due to the growth of numbers in active RIPE Atlas anchors, we started involving more anchors from outside our service region in DNSMON measurements. This has a natural effect on the visualisations: the newly involved anchors don't have a measurement history yet, so they show up as "no data" before the addition. We're introducing these changes gradually for the monitored zones so the changes are not yet visible everywhere. Regards, Robert Kisteleki

4 5

DNSMON visualisation delay
by Robert Kisteleki 08 Jul '14

08 Jul '14

Dear DNS Working Group, At RIPE68 we were asked to "send an email to the mailing-list about advantages and disadvantages of delayed and non-delayed versions of DNSMON [visualisation], specifically related to the management of the software and the ongoing maintenance of the legacy systems that you want to retire". As many of you know, the old DNSMON service had an artificial delay of a couple of hours for visualising the incoming data, for everyone except a specific "DNSMON customers" group. With the changes to the service model as of 2013 there is no good definition of "DNSMON customers" any more. Also, the current DNSMON implementation does not apply any artificial delays, which in practice means all data points show up in the graphs within 10-15 minutes. As Daniel projected a few days ago, we see some realistic options regarding this visualisation delay: === 1. No changes to what the service offers now; ie. graphs will show results with minimum delay Development effort: none Pro: simplest solution Con: this is perceived by some to be "helping potential attackers" by making it easy to observe the effects of an attack on the DNS infrastructure === 2. Introduction of an artificial delay to *all* users, regardless of NCC member/non-member, or login status (known an anonymous users) Development effort: minimal (est. couple of developer days) Pro: not helping potential bad guys monitoring the zones/servers in real time Con: not helping the good guys monitoring the zones/servers in real time either === 3. Introduction of an artificial delay to users in general, except for RIPE NCC members. Authentication is done by RIPE NCC Access (Single Sign-On), authorization is controlled by the existing LIR portal mechanism. Development effort: minimal (est. couple of developer days) Pro: RIPE NCC members have early access to visualisations, others don't Note: the current number of SSO account belonging to RIPE NCC members is ~24000 Note: we may or may not help the attacker, depending on whether (s)he is a member of the RIPE NCC or not === 4. Introduction of an artificial delay to users in general, except for a specially designated DNSMON customers (zone operators) group. Authentication is done by RIPE NCC Access (Single Sign-On), authorization is controlled by a vetting process managed by the RIPE NCC. Development effort: moderate (est. more than a couple of developer days) Con: administration overhead is non-trivial -- we'll have to establish and keep tracking who is in the privileged group and who isn't; with people joining/leaving organisations this could be tricky and diverge from reality. Pro: members of the special group have early access to visualisations, others don't Note: people in this special group can come from organisations which may or may not be RIPE NCC members. Note: we may or may not help the attacker, depending on whether (s)he is a member of this group or not Please give us guidance about your your preferred solution by replying to this mail to the list. Regards, Robert Kisteleki RIPE NCC

4 3

Closure of Test Traffic Measurements Service and Changes to the DNS Monitoring Service
by Romeo Zwart 07 Jul '14

07 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear colleagues, As of 1 July 2014, the old DNS Monitoring Service (DNSMON), based on the Test Traffic Measurements Service (TTM), has stopped receiving updates to its data. The new DNSMON interface is available at: https://atlas.ripe.net/dnsmon All historic DNSMON visualisations will remain available at: http://dnsmon-old.ripe.net We will keep these visualisations of the historic data available until at least the end of 2014. Existing URLs that point to specific periods or zones in the old DNSMON (for example http://dnsmon.ripe.net/dns-servmon/server/) will be redirected and will continue to work for as long as the old DNSMON visualisation servers are maintained. As discussed at the RIPE 68 DNS Working Group session in Warsaw, the RIPE NCC will provide some statistics on usage of the old visualisations at RIPE 69 in London. The DNS Working Group will be consulted regarding the further maintenance or possible decommissioning of these visualisations. Background The RIPE NCC announced a new version of DNSMON in March 2014 and informed the community that the old DNSMON would be phased out. The old DNSMON was dependent upon measurements run as part of TTM, which was in the last phase of its existence. TTM has been decommissioned, as announced previously, on 1 July 2014. In line with the closure of TTM, data collection in the old DNSMON has also been terminated from that same date. These changes are in line with our previous communications, notably the RIPE Labs article "Timeline for Phasing Out the Old TTM-Based DNSMON": https://labs.ripe.net/Members/romeo_zwart/copy_of_proposed-time-lines-for-p… Romeo Zwart RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO6fx4ACgkQGRL9suBV+eos8ACfUMImGvgAV9rJ1bxzLbt4hLmv HewAni2DYCGSLAWOAhYREtCsprGj8jKR =gI+O -----END PGP SIGNATURE-----

1 0

Call for joining RSSAC Caucus
by Tripti Sinha 25 Jun '14

25 Jun '14

Dear colleagues, This is a friendly reminder to apply for RSSAC Caucus membership. The cut-off date for first round of membership is end of June, so please kindly submit your statement of interest before 1st of July<x-apple-data-detectors://0> to rssac-membership(a)icann.org<mailto:rssac-membership@icann.org>. On Monday 23rd of June RSSAC had its public session at ICANN 50 and it was announced that the first face to face caucus meeting will be held during IETF 90 in Toronto. Kind regards, Tripti Sinha on behalf of RSSAC Caucus membership committee

1 0

Call for joining RSSAC Caucus
by Tripti Sinha 18 Jun '14

18 Jun '14

Greetings, If you are interested in participating at ICANN's Root Server System Advisory Committee (https://www.icann.org/resources/pages/charter-2013-07-14-en) as a Caucus member, please kindly read the relevant information and Caucus document published at https://www.icann.org/resources/pages/rssac-caucus-2014-05-06-en and submit your statement of interest to rssac-membership(a)icann.org<mailto:rssac-membership@icann.org>. The RSSAC executive is working on publishing the final version of "Procedures documents" and at the moment is establishing the Caucus with a few work items ready to be discussed by the Caucus. If you would like to volunteer please kindly indicate those intentions known by sending an email to rssac-membership(a)icann.org<mailto:rssac-membership@icann.org>. Kind Regards, Kaveh Ranjbar, RSSAC Membership Committee Chair Tripti Sinha, RSSAC Membership Committee Member Paul Vixie, RSSAC Membership Committee Member

1 0

DNSMON changes
by Jim Reid 06 Jun '14

06 Jun '14

Although the WG's response to the NCC's proposal has been disappointing, there have been three statements of support (one with qualifications) and none against. It had been stated that silence implied consent. Since no objections have been raised, the WG has reached a decision that has lightweight consensus. Though not a formal consensus as would be understood in the context of the PDP. Which is OK as this issue is not in PDP territory anyway. Therefore the NCC should proceed as planned and published at: https://labs.ripe.net/Members/romeo_zwart/copy_of_proposed-time-lines-for-p… The points made by Peter and Daniel are worth further discussion and I encourage you all to do that. On one hand, there could be some benefit in providing "backwards compatibility" for visualising old data. OTOH, this may put an unreasonable burden on the NCC by creating an open-ended commitment to support legacy cruft and result in users who can't/won't migrate to the current platform. It would be good for WG members to express their opinions about this. My personal view is somewhere inbetween: provide some way of visualising the old data if that can be done with minimal effort/resources from the NCC on a best efforts, unsupported basis. If that facility later dies, it dies and that's the end of the matter. YMMV.

3 2

indulgence satiated
by manning bill 05 Jun '14

05 Jun '14

Thanks All for taking the time to prod 2001:500:84::b Looks like it is reachable from many places… enough that we will proceed to augment the “B” root server with perhaps the last in a long line of IPv6 addresses that it has had over the last 15 years. Splay will increase over time. /bill /bill Neca eos omnes. Deus suos agnoscet.

4 7

WG comment on DNSMON changes
by Jim Reid 03 Jun '14

03 Jun '14

Colleagues, you might recall that last month the NCC announced a time-line for some changes to the DNSMON service. This was discussed when the WG met in Warsaw last week. In outline, the old service is based on TTM boxes which are due to be retired at the end of June. These are already beyond their anticipated life-span. The new version of DNSMON uses the Atlas probes and is already operational. It is possible some users of DNSMON may need to change their internal tools and processes when transitioning to the new platform if these depend on the data gathering done by the soon-to-die TTM boxes. If this affects you, please speak up now! I would be grateful if you could express your approval or rejection of the NCC's approach and proposed time-line. Details are at https://labs.ripe.net/Members/romeo_zwart/copy_of_proposed-time-lines-for-p…. There was little to no response by the WG to the earlier announcement. This makes both your WG Co-chairs and the NCC staff uncomfortable. After the WG co-chairs and NCC's DNSMON team discussed this last week, we agreed to set the end of this month as the final date for comments. Although we can work on the operating principle that silence implies consent, it would be better for all concerned if there were positive messages of support (or even ones of objection) on the list. Please respond. I'd appreciate it if you can comment on the list to indicate that you approve (or disapprove) of the current proposal and/or time-line. thanks in advance

7 6

crave your indulgence
by manning bill 28 May '14

28 May '14

If you wouldn’t mind a quick tracerooute - Can you confirm reachability to the following: 2001:500:84::b Thanks in advance. /bill Neca eos omnes. Deus suos agnoscet.

5 5

Provisional agenda for RIPE 68
by Jim Reid 07 May '14

07 May '14

Colleagues, my apologies for the delay in getting the agenda prepared and distributed for next week. At long last, here it is. Please note one or two items have not get been confirmed, so there may be some changes between now and next Wednesday. Although I don't expect there will be any, it would be unwise to make life-changing decisions on the assumption that the V1.4 agenda remains unchanged. Hope to see most of you in Warsaw next week. # # $Id: agenda,v 1.4 2014/05/07 11:00:29 jim Exp $ # PROVISIONAL AGENDA: RUNNING ORDER, TIMES & EVEN CONTENT MAY CHANGE [0] Usual Administrivia 5 mins Agenda bashing Minutes of previous meeting Review of Action Items [1] NCC Report 15 mins Stuckee, RIPE NCC [2] DDoS Forensics 25 mins Curon Davies, JISC RSC Wales As a result of daily attacks against a Further Education College in Wales, a connection was noticed between changing DNS entries and the attacked IP address. Using innovative DNS responses inspired by GeoDNS and logging all requests to the authoritative server, it has been possible to trace the source of DDoS and spoofed flood attacks. [3] Measuring DNSSEC validation deployment 15 mins Nicolas Canceill, NLnet Labs We have executed a research in which the RIPE Atlas measurement network was utilized to quantify the amount/percentage of resolvers that do DNSSEC validation. We were not only able to identify which resolvers do DNSSEC validation, but also which resolvers are security-aware (and to which level). Moreover, during the research some particular cases have been found: the existence of insecure fallbacks in case of missing signatures, and a troublesome issue with secure wildcard records. [4] Measuring DNSSEC from the end user perspective 30 mins Geoff Huston, APNIC The presentation explores the technique of measuring the characteristics of the DNS and its performance by posing a set of DNS questions to end users and observing the queries that occur at the authoritative servers in response. Using online advertising channels the tests can be undertaken at a level of high volume and broad spread across the Internet. The presentation will describe the use of this technique in measuring DNSSEC validation, DNS over TCP, DNS performance and similar. LUNCH [5] Report from Ad-hoc ccTLD group 10 mins Peter Koch, DENIC [6] Registry Infrastructure Transformation 20 mins Michael Daly, Nominet In the past 24 months Nominet the UK Registry have completely transformed the infrastructure that is used to deliver the UK Registry services. The infrastructure has been moved to be much more agile and highly available. This presentation will detail some of the choices we made and methods we used to deploy and manage our infrastructure. [7] Google DNS hijacking in Turkey 30 mins Stephane Bortzmeyer, AFNIC In March 2013, the Turkish government decided to prevent access to Twitter. It used some well-known techniques but also one which have not been documented in the real world before: using routing to hijack DNS resolvers such as Google Public DNS. What exactly happened and what could be done to prevent that? [8] DNSMON Developments 10 mins Stuckee, RIPE NCC [9] DNS Monitoring Common Practices/APIs Panel Session 15 mins To be confirmed [10] AOB 5 mins

2 1