This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
- Previous message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
- Next message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Oct 18 11:44:29 CEST 2016
> On 18 Oct 2016, at 09:54, Romeo Zwart <romeo.zwart at ripe.net> wrote: > > The proposal submitted by VeriSign Sàrl (“Verisign”) was the best fit. > We subsequently signed a contract with Verisign, which comes into effect > before the end of this year. The contract is for the period of one year, > with the intention to renew yearly. Prior to renewal, we will look at > the benefits of the service and actual market situation at that time to > decide on renewing the service. Thanks Romeo. This is great news. Bringing in a competent DNS hosting provider will add diversity and resiliance to the DNS infrastructure for ripe.net. It’s also good that these new arrangements are documented in a contract. I’m sure the WG agrees. Well, I hope it does... :-) I’m sure you’ll keep the WG informed of how this works out and what happens when the contract comes up for renewal. My thanks and appreciation to your team for the hard work of preparing and running the RFP and arranging the contract with the supplier.
- Previous message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
- Next message (by thread): [dns-wg] Verisign to provide secondary DNS services for the RIPE NCC’s zones
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]