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] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
- Previous message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
- Next message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bjørn Mork
bjorn at mork.no
Wed Oct 14 22:44:52 CEST 2015
Keith Mitchell <keith at dns-oarc.net> writes: > As the loose co-ordinator of the AS112 project, OARC has been looking > recently at ways of improving measurement of the aforementioned crap > signal. If you are a large IXP or eyeball-ISP operator who would like to > co-operate with OARC on operating and/or data-gathering AS112 nodes, > we'd love to hear from you. Completely off topic, but this discussion made me look at the https://www.as112.net/ site again, only to be greeted by a terrifying(?) red icon by the TLSA validator plugin (https://www.dnssec-validator.cz/) Is it only me, or did someone forget to add a new TLSA record for _443._tcp.www.as112.net before changing the certificate? Yes, yes, I know, nobody are able to manage those records and the certificate is only a few hours old. But still :) Bjørn
- Previous message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
- Next message (by thread): [dns-wg] New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]