April 2022 - dns-wg - mailman.ripe.net

Changes to Time-to-Live (TTL) values in reverse DNS zones
by Anand Buddhdev 22 Apr '22

22 Apr '22

Dear colleagues, In 2021, we announced a plan to change the time-to-live (TTL) values in the reverse DNS zones that we maintain. You may view the announcement here: https://www.ripe.net/ripe/mail/archives/dns-wg/2021-November/003928.html Many members of the community expressed support for our proposal. Therefore, we are going to make these changes next week on Wednesday 20 April. We will lower the TTL of NS records to 86400 (1 day) and that of DS records to 3600 (1 hour). Note that the TTL of records imported from other Regional Internet Registries (RIRs) will not be affected. Those records will be imported with the TTLs as published by the origin RIR. Regards, Anand Buddhdev RIPE NCC

5 9

New on RIPE Labs: Detecting DNS Root Manipulation
by Alun Davies 19 Apr '22

19 Apr '22

Dear colleagues, In 2021, when reports emerged that hosts in Mexico were unable to reach whatsapp.net, it was determined that middleboxes were to blame. These devices were intercepting the queries to the root instance hosted in China and sending a bogus reply. Taking this as their starting point, Qasim Lone and colleagues have been investigating the prevalence of middleboxes using RIPE Atlas: https://labs.ripe.net/author/qasim-lone/detecting-dns-root-manipulation/ Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

DNS4EU
by Andrew Campling 19 Apr '22

19 Apr '22

Tomorrow is the revised deadline for responses to the European Commission's DNS4EU Call for Proposals. I don't have the impression that there will be a large number of responses from the industry, does anyone have a different perspective? Andrew

1 0

.arpa ns changes
by James Mitchell 15 Apr '22

15 Apr '22

Dear network operators and other interested parties: This is advance notice that beginning 25 April, the hostnames for the nameservers for the .ARPA zone are planned to change. The new names will correspond to the same IP addresses that already provide the service. This change is planned occur in two phases. On Monday, April 25, the A, C, and E nameservers will change to their new hostnames. The remaining nameservers will change one week later on Monday, May 2. We do not expect any issues to arise from these changes. The work is being done as described in RFC 9120, in coordination with our root zone management partner Verisign and the IAB. Kind regards, James Mitchell Internet Assigned Numbers Authority

1 0