Re: [dns-wg] Co-chair nomination
Dear all, First of all I would like to say thanks to Peter because he did a very good work as Co-chair of this working group. I would like to nominate Dave Knight as co-chair of the DNS working group. I have known Dave for many years. I think both his technical knowledge and his attitude make him very suitable for this position. I would like to express my support for his nomination. Best regards, Janos
Re: [dns-wg] RIPE NCC secondary name services for ccTLDs
Dear Romeo, At RIPE 68 you, the working group, provided us with some guidelines regarding the eligibility of new zones to be added to this service. We intend to document these guidelines in the form of a new RIPE Document*, of which a draft version is attached to this email. We welcome any comments you may have on this document. Thank you for this document. I think it reflects very nicely all the aspects discussed by the ad-hoc group and by the DNS-WG at RIPE 68. I have a small comment regarding the first bullet of point 4., which now reads: "If the number of delegations in the zone, or in any of its child zones, exceeds 10,000..." I think this clearly refers to any public child zone, i.e. a child zone that is administered by the ccTLD itself, and not to a delegated zone managed by a third party. Therefore I suggest adding the word "public" before "child". Best regards, Janos Kind regards, Romeo Zwart
Re: [dns-wg] DNS WG co-chair nomination
Dear DNS WG, I nominate myself as co-chair of the DNS working group. I support Shane as co-chair. I think you’re a great fit for the role. I agree with Nurani. I also support Shane, who has been working in the DNS area for a long time. Best regards, Janos Cheers, Nurani
Re: [dns-wg] 2017 dns-wg co-chair appointment
Dear all, With this email I would like to put my name forward as a candidate for the DNS WG cochair role as announced yesterday by the current co-chairs. I have been involved in the DNS WG at RIPE for a long time, contributing when and where possible throughout the years during my time at the RIPE NCC, ISC, Dyn, Bondis and APNIC. This trajectory has made me fairly familiar with the DNS world, its history and evolution as well as the current topics under discussion. I support Joao's nomination. I think he is an excellent candidate and will be a good co-chair for the WG. Best regards, Janos
[dns-wg] KSK Rollover Postponed
Dear all, https://www.icann.org/news/announcement-2017-09-27-en Strange enough, I did not see any mail/announcement about this on this list. I suppose not everybody on this list was aware. I hope we can hear some background information at RIPE 75. Best regards, Janos
Re: [dns-wg] SLD .gov.* within european countries
Dear Antonio, I hope you can help me on a not-so-related-to-DNS question. does the SLD .gov.* within european countries' ccTLDs identify only central government bodies and not local government or other public administrations as well? gov.hu is a protected name. The registry delegates it only to a central government designated body. What it is used for, is up to them. As far as I can tell, it is used only by central government, but they could allow any other use too. Local governments usually use the name of the city/village as it is reserved for them. I hope this helps. Best regards, Janos thank you -- antonio
Re: [dns-wg] Volunteer list for RIPE DNS working group chair
Dear DNS working group, Please offer whatever support (or opposition) you have for Dave on the list. I do support Dave. I think he did a good job so far and I am glad he is willing to continue. Also, I have no problem with having a single candidate this time. Best regards, Janos Thank you Dave for volunteering! Cheers, -- Shane On behalf of the DNS working group chairs
Re: [dns-wg] Volunteer to co-chair the DNS wg
Dear all, Please offer whatever support (or opposition) you have for Shane on the list. I strongly support Shane. Thank you Shane for volunteering! +1. Best regards, Janos dave
Re: [dns-wg] Volunteer list for RIPE DNS working group chair
Dear all, ... a single volunteer, Joao Damas. Please offer whatever support (or opposition) you have for Joao on the list. I fully support Joao. I am glad he is willing to serve another term. Best regards, Janos Thanks, dave, for the DNS wg chairs
Re: [dns-wg] Volunteer list for RIPE DNS working group chair
Dear Randy, With all respect my respect for you, I still support Joao. o we might think about term limits I think putting a term limit may prevent talented people from serving the community in spite of their willingness to continue their useful work. If there were many candidates with similar qualities, I would have no problem with asking for change. Best regards, Janos randy -- [0] idiom meaning to walk what we talk [1] [1] idiom meaning to do as we say :)
Re: [dns-wg] post-mortem for ripe.net DNSSEC problem on 1 November 2023
Dear Paul, Please find below the post mortem for the DNSSEC problem that caused most of RIPE NCC's services to become unavailable yesterday. Thank you very much for the detailed post-mortem. Please reach out if you have any questions or feedback. I would like to comment on a single item, see below. New or changed records were still properly signed (363 of them), which meant that our monitoring, which checks the signature validity of the SOA record at the zone apex, missed this issue. It may be a good idea to check for the lowest timestamp of signature validity (of the RRSIG records) in the zone. We monitor this for .hu from the beginning (i.e. since we started signing the zone with DNSSEC). Best regards, Janos -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/dns-wg
Re: [dns-wg] Retiring ns.ripe.net
Dear all, We are proposing to retire the secondary DNS service by the end of 2024 and we're asking for your input and feedback on this proposal. I agree with the proposal. I also agree with the recommendation to stop the service at a different time than the end of the year holidays. I saw there are 663 broken delegations. I understand most of these (if not all) are such that ns.ripe,net cannot download the zone from the master. I am wondering whether there are also cases when the master does not even have the ns.ripe.net configured as NS - I suspect there are. Anyway, in case of the broken delegations I would recommend to consider decommissioning them from the very beginning (1 July 2024). This means that ns.ripe.net (and other servers involved, e.g. transfer servers) would ignore these zones (i.e. these zones would be deleted from their configuration). This would free up some of the NCC resources. The difference would be that ns.ripe.net would answer with REFUSED instead of SERVFAIL. I would go even further, I would delete the delegation to ns.ripe.net from the parent zone (usually the /8 for IPv4) - this way there would be much less unanswerable traffic going to ns.ripe.net. I think it would be better to not touch the domain objects at this time, and process them together with the correct delegations. Best regards, Janos Paul de Weerd Manager Global Information Infrastructure team RIPE NCC -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/dns-wg
