- dns-wg - mailman.ripe.net

PowerDNS vulnerabilities
by Jim Reid 28 Nov '17

28 Nov '17

A bunch of vulnerabilities have been found in the Authoritative and Recursor servers. Here’s the list of security advisories: http://seclists.org/oss-sec/2017/q4/329 I’m surprised this hasn’t been mentioned on these lists yet.

3 4

FOSDEM 2018 DNS devroom Call for Participation (CfP)
by Shane Kerr 20 Nov '17

20 Nov '17

RIPE DNS Enthusiasts, FOSDEM is the Free and Open Source Developers European Meeting. If you are involved in any way with open source software and can get the weekend free, it is very cool. This year we will have a DNS devroom. Read on... [ The text below has also been posted at: https://blog.powerdns.com/2017/11/20/fosdem-2018-dns-devroom-cfp/ If anything changes, we'll update that post, so please check there if you have questions. Also, our apologies if you receive multiple copies of this CfP via different mailing lists. ] After two successful BoF sessions at FOSDEM 2016 and 2017, FOSDEM 2018 will see a real DNS devroom! We hope to host talks anywhere from hardcore protocol stuff, to practical sessions for programmers that are not directly involved with DNS but may have to deal with DNS in their day to day coding, or system administrators responsible for DNS infrastructure. We have been allotted half a day on Sunday 4 February 2018. We expect to schedule 30 minutes per talk, including questions, but this is open to discussion. If you have something you'd like to share with your fellow developers, please head to pentabarf at: https://penta.fosdem.org/submission/FOSDEM18 Examples of topics are measuring, monitoring, DNS libraries, and anecdotes on how you've (ab)used the DNS. The deadline for submission is December 8th. If you have a FOSDEM pentabarf account from a previous year, please use that account. Reach out to dns-devroom-manager(a)fosdem.org if you run into any trouble. We are also looking for volunteers to help with cameras etc. Please drop us an email at dns-devroom-manager(a)fosdem.org if you're interested in helping out. See you there! Cheers, Peter van Dijk, Shane Kerr, Pieter Lexis

1 0

New on RIPE Labs: Verfploeter: Broad and Load-aware Anycast Mapping
by Mirjam Kuehne 13 Nov '17

13 Nov '17

Dear colleagues, Here is a summary of a research paper written by Wes Hardaker, Wouter de Vries and Ricardo Schmidt: Verfploeter: Broad and Load-aware Anycast Mapping IP anycast provides DNS operators and CDNs with automatic fail-over and reduced latency by breaking the Internet into catchments, each served by a different anycast site. https://labs.ripe.net/Members/wouter_de_vries/verfploeter-broad-and-load-aw… Kind regards, Mirjam Kühne RIPE NCC

1 0

Fwd: [dns-operations] Update on root KSK roll project
by Shane Kerr 08 Nov '17

08 Nov '17

Hello RIPE DNS working group, Here is a message from Matt Larson about the status of the root KSK roll for anyone who is not on the dns-operations mailing list and might find it useful or interesting. Cheers, -- Shane

1 0

New on RIPE Labs: Anycasting AS197000 More Widely
by Mirjam Kuehne 06 Nov '17

06 Nov '17

Dear colleagues, We are working on an experiment to see if we can increase the capacity and resiliency of the RIPE NCC's authoritative DNS service (AS197000). This service hosts all the reverse DNS zones, ripe.net and provides secondary service for various ccTLDs. Please find more details on RIPE Labs: https://labs.ripe.net/Members/anandb/anycasting-as-197000-more-widely Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: A Software-based Approach to Identify Heavy Hitters in DNS Traffic
by Mirjam Kuehne 25 Oct '17

25 Oct '17

Dear colleagues, Please find this new article on RIPE Labs, contributed by Santiago Ruano Rincon, one of the RACI fellows from RIPE 74: A Software-based Approach to Identify Heavy Hitters in DNS Traffic This article presents a software-based prototype able to estimate the most queried domain names in a stream of DNS traffic at 12Mpps (wire-rate 10GbE). The goal is to identify domains involved in random qname attacks. This prototype is a proof-of-concept of our research on software and commodity-hardware approaches to analyse high-speed network streams. https://labs.ripe.net/Members/santiago_r_r_/a-software-based-approach-to-id… Kind regards, Mirjam Kuhne RIPE NCC

1 0

New on RIPE Labs: The Future of DNSSEC at the RIPE NCC
by Mirjam Kuehne 24 Oct '17

24 Oct '17

Dear colleagues, DNSSEC signing solutions and products have evolved greatly since we first began signing our zones. We are now exploring ways of doing it better and smarter. Please read about our plans on RIPE Labs: https://labs.ripe.net/Members/anandb/the-future-of-dnssec-at-the-ripe-ncc Anand will present this during the DNS WG session at RIPE 75. Kind regards, Mirjam Kuhne RIPE NCC

1 0

Draft minutes from the DNS working group at RIPE 74
by Shane Kerr 23 Oct '17

23 Oct '17

DNS Colleagues, Draft minutes from the DNS working group at RIPE 74 are available here: https://www.ripe.net/participate/ripe/wg/dns/minutes/dns-working-group-minu… Please send any corrections to the DNS working group chairs at <dns-wg-chairs(a)ripe.net>. [ Apologies for the late e-mail notice. These were actually posted by the RIPE NCC on 2017-06-20, but I did not send this to the list. :( ] Cheers, -- Shane

1 0

f.root-servers.net problem - UA-IX exchange point
by Сергій Співак 22 Oct '17

22 Oct '17

Hello, There is a problem with a F root-server node connected to UA-IX traffic exchange point (ix.net.ua, AS15645) since October, 14. IP 192.5.5.241 is unreachable from our AS48438 since this date. Troubleshooting of this problem shows trace broken at: 5 2 ms 2 ms 1 ms kbp1b.f.root-servers.ix.net.ua [195.35.65.250] 6 2 ms 1 ms 1 ms iana.r1.kbp1.isc.org [192.228.86.1] 7 * * * Request timed out. 8 * * * Request timed out. IP 192.5.5.241 is also unreachable from UA-IX looking glass ( http://lg.ix.net.ua/ ): Command: ping ipv4 Parameter: 192.5.5.241 ________________________________ Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.5.5.241, timeout is 2 seconds: ...U. Success rate is 0 percent (0/5) The route for 192.5.5.0/24 is present in routing database ( http://lg.ix.net.ua/ ): Command: show ipv4 bgp Parameter: 192.5.5.0/24 ________________________________ BGP routing table entry for 192.5.5.0/24, version 47209171 BGP Bestpath: deterministic-med: cost-community-ignore Paths: (2 available, best #1, table default) Advertised to update-groups: 73 74 76 194 231 233 Refresh Epoch 1 30128 3557, (aggregated by 30128 192.228.86.16) 185.1.50.250 from 185.1.50.250 (192.228.86.17) Origin IGP, metric 2, localpref 100, valid, external, atomic-aggregate, best Community: 3557:10 15645:5 rx pathid: 0, tx pathid: 0x0 Refresh Epoch 1 30128 3557, (aggregated by 30128 192.228.86.16) 185.1.50.248 from 185.1.50.248 (192.228.86.16) Origin IGP, metric 12, localpref 100, valid, external, atomic-aggregate Community: 15645:5 rx pathid: 0, tx pathid: 0 Please fix it. Thanks. -- Best wishes, Sergii Spivak www.corbina.com.ua

3 2

Decommissioned anchors replaced in DNSMON
by Chris Amin 17 Oct '17

17 Oct '17

Dear colleagues, You may noticed that the number of anchors actively participating in DNSMON had recently decreased somewhat. This is because they were version 1 anchors that had been decommissioned. In most cases, these anchors have since been upgraded to version 3 anchors. We have now added those replacements anchors to the DNSMON set, so you will notice new lines in the DNSMON graph on the probe view, and aggregated values of the server view will be affected slightly. For more information on version 3 anchors, see: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors Kind regards, Chris Amin RIPE NCC

1 0