- dns-wg - mailman.ripe.net

NCC reverse delegation criteria
by Måns Nilsson 11 Jun '19

11 Jun '19

Recently, a discussion regarding the checks performed by the NCC before reverse delegation is made came up on the members-discuss list. It was concluded that this should be discussed here rather than there. The members archive might not be available to all, so I'll try to summarize. Please add your take on summary if you find mine lacking. The questioned practice was that the NCC rejects the delegation request if the target server is found to be an open recursor. Some participants argued that this is not a technical problem, and some said yes it is. Some held that the NCC has no authority blocking a request, but it was argued that every delegation is subject to RFC 1591 responsibilites. For starters, are the delegation requirements described somewhere? Best regards, -- Måns Nilsson primary/secondary/besserwisser/machina MN-1334-RIPE SA0XLR +46 705 989668 In 1962, you could buy a pair of SHARKSKIN SLACKS, with a "Continental Belt," for $10.99!!

9 12

RIPE 78 DNS working group final agenda
by Shane Kerr 20 May '19

20 May '19

Colleagues, Here's a (hopefully) final agenda for the DNS working group session in RIPE 78. Peter Špaček's presentation on the DNS Flag Day 2019 will be given at the RIPE Plenary on Tuesday, and not at the DNS working group session. We also added a couple of short presentations from the RIPE NCC, one general update and another about the recent work on ENUM that they have been doing. We're meeting on Thursday 23 May from 16:00 to 17:30. 1. Administrivia 5 minutes 2. RIPE NCC DNS Update by Anand Buddhdev 5 minutes 3. ENUM Cleanup by Marco Hogewoning 5 minutes 4. Overview of the DNS Privacy Software landscape by Carsten Strotmann 30 minutes 5. unwind, a validating DNS recursive nameserver by Carsten Strotman 5 minutes 6. Tag You're It!: Revisiting the Reality of DNSSEC Keytags by Roland M. van Rijswijk-Deij 15 minutes 7. root KSK Rollover Wrap-up by the DNS working group chairs 15 minutes 8. DNS-OARC Summary by Dave Knight 10 minutes Skál, -- The RIPE DNS Working Group Chairs Dave, João, and Shane

2 1

Draft minutes from the DNS working group at RIPE 77
by Shane Kerr 13 May '19

13 May '19

DNS Colleagues, Draft minutes from the DNS working group at RIPE 77 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>. Cheers, -- Dave, João, and Shane RIPE DNS Working Group Chairs

1 0

Revised Operating Instructions for e164.arpa (ENUM)
by Marco Hogewoning 03 May '19

03 May '19

Dear colleagues, The RIPE NCC is the operator of the e164.arpa zone (ENUM) and maintains the associate registry in accordance with the instructions of the Internet Architecture Board (IAB). As delegations are based on E.164 country code allocations, any changes to the registry are coordinated with and approved by the respective holders of the E.164 country code via the ITU’s Telecommunications Standardisation Bureau (TSB). Recent checks have shown that over time, many of the current 57 delegations have deteriorated – they are no longer technically functional or the contacts details for the country code registry have not been updated. Seeking advice from the IAB on these matters, they agreed to revise the instructions to address these issues. Among the changes is new text regarding the deletion of delegations and instructions that allow the RIPE NCC to do periodic checks on registry data. This will allow us to initiate a process to review the existing delegations and coordinate with the registries, governments and the TSB to mitigate and correct any errors. In cases where we are unable to correct an error, we will advise the government involved to remove the delegation, until such time that a new registry can assume responsibility for the country code and restore its technical functionality. ITU Study Group 2, which is responsible for the E.164 number registry, shared our concerns and at its last meeting agreed to update its instructions to the TSB to reflect these changes. As we remain committed to coordinating any delegations with TSB, the Member States involved and Study Group 2, we welcome the study group’s renewed interest in the topic and its support in reviewing and updating these registrations. The new instructions have now been published on our website and, with the IAB’s approval, we will now operate the registry in accordance with these. The instructions are available here: https://www.ripe.net/manage-ips-and-asns/dns/enum/iab-instructions Kind Regards, Marco Hogewoning Senior External Relations Officer, RIPE NCC, Ted Hardie For the IAB

3 2

Re: [dns-wg] New on RIPE Labs: Making the DNS More Private with QNAME Minimisation
by Wouter de Vries 29 Apr '19

29 Apr '19

On Mon, Apr 29, 2019 at 08:43:52AM +0100, Piete Brooks wrote: > > In the case your resolver was doing qmin, the third line should have read something like: > > myip -> 185.49.141.12 TXT b.qnamemin-test.internet.nl (omitting the last label: a). > > And a second typo would allow me to understand it - was that a TXT or an NS lookup? I blame it on early monday. That should have been NS indeed :-). Also your other comment about the IP is correct, sorry about that. So the final request/response sequence should happen between myip and 185.49.141.13.

1 0

New on RIPE Labs: Making the DNS More Private with QNAME Minimisation
by Mirjam Kuehne 29 Apr '19

29 Apr '19

Dear colleagues, DNS queries can contain a lot of sensitive information about Internet users. Query name minimisation (qmin) limits the information revealed to what is actually necessary for a DNS name server to answer the query. Woute de Vries, Moritz Mueller and others did a study on qmin deployment and the associated challenges: https://labs.ripe.net/Members/wouter_de_vries/make-dns-a-bit-more-private-w… Kind regards, Mirjam Kühne RIPE NCC

5 5

RIPE 78 DNS working group draft agenda v2
by Shane Kerr 10 Apr '19

10 Apr '19

Colleagues, Here's an updated draft agenda for the DNS working group session in RIPE 78 (we overlooked an interesting submission from Roland van Rijswijk-Deij). We're meeting on Thursday 23 May from 16:00 to 17:30. 1. Administrivia 5 minutes 2. Overview of the DNS Privacy Software landscape by Carsten Strotmann 30 minutes 3. unwind, a validating DNS recursive nameserver by Carsten Strotmann 5 minutes 4. DNS flag day 2019 and beyond by Petr Špaček @ CZ.NIC 15 minutes 5. Tag You're It!: Revisiting the Reality of DNSSEC Keytags by Roland M. van Rijswijk-Deij 15 minutes 6. root KSK Rollover Wrap-up by the DNS working group chairs 15 minutes 7. DNS-OARC Summary by Dave Knight 10 minutes See you in Reykjavík! -- The RIPE DNS Working Group Chairs Dave, Joao, and Shane

1 0

RIPE 78 DNS working group draft agenda
by Shane Kerr 08 Apr '19

08 Apr '19

Colleagues, Here's a draft agenda for the DNS working group session in RIPE 78. We're meeting on Thursday 23 May from 16:00 to 17:30. 1. Administrivia 5 minutes 2. Overview of the DNS Privacy Software landscape by Carsten Strotmann 30 minutes 3. unwind, a validating DNS recursive nameserver by Carsten Strotmann 5 minutes 4. DNS flag day 2019 and beyond by Petr Špaček @ CZ.NIC 15 minutes 5. root KSK Rollover Wrap-up by the DNS working group chairs 20 minutes 6. DNS-OARC Summary by Dave Knight 10 minutes See you in Reykjavík! -- The RIPE DNS Working Group Chairs Dave, Joao, and Shane

1 0

Call for contributions to the RIPE 78 meeting of the dns-wg
by Dave Knight 02 Apr '19

02 Apr '19

Dear colleagues, The RIPE 78 meeting in Reykjavik is a few weeks away and we’d like to form our agenda. Please submit your presentation ideas, or suggestions for discussions to <dns-wg-chairs(a)ripe.net>. Please don’t submit anything using the meeting submission web form, it’s not intended for submission of content to working groups. Thanks! dave, on behalf of the working group chairs

2 2

How to determine the last message in sequence in DNS TCP responce
by Владимир Мартьянов 27 Feb '19

27 Feb '19

I make DNS zone transfer request (aka AXFR) via TCP to the server. The answer is too big (>100Kb), so it could not be sent in one TCP message. So the server send me a sequence of messages. How can I determine which message is the last? I can't found anything about it's count in the first message. I can't found any special flag in the last one. I can't found anything about it in RFC1035. Could you please explain how to find "end of answer"?

3 2