[dns-wg] RIPE NCC DNSSEC trust anchors
- Previous message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
- Next message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
Woeber at CC.UniVie.ac.at
Thu Nov 13 16:18:01 CET 2014
Well, this may be seen as a stupid question from a DNS DAU, but can you explain what ripe.int (an international treaty organisation?) and ripen.cc are used for? Thanks, Wilfried Anand Buddhdev wrote: > Dear colleagues, > > Most of the zones that the RIPE NCC signs with DNSSEC have trust anchors > in their parent zones, with the exception of these three zones: > > 151.76.62.in-addr.arpa > ripe.int > ripen.cc > > We have been publishing trust anchors for these three zones on our > website, as well as in the ISC DLV trust anchor repository (TAR): > https://dlv.isc.org > > On Tuesday, 11 November 2014, we rolled our DNSSEC Key Signing Keys > and added the new trust anchors for these three zones to the ISC > DLV TAR. Because we believe manual configuration of trust anchors is > very rare these days, we are taking this opportunity to stop publishing > trust anchors for these three zones on our website. The trust anchors > remain available via the ISC DLV TAR. Of course, as soon as we are > able to publish DS records for these zones in their parents, we will > do so and withdraw them from the ISC DLV TAR, as we have done for all > our other zones. > > If you have any questions or concerns, please send email to dns at ripe.net. > > Regards, > > Anand Buddhdev > Senior Engineer > RIPE NCC
- Previous message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
- Next message (by thread): [dns-wg] RIPE NCC DNSSEC trust anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]