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] NCC reverse delegation criteria

Previous message (by thread): [dns-wg] NCC reverse delegation criteria
Next message (by thread): [dns-wg] NCC reverse delegation criteria

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Rubens Kuhl rubensk at nic.br
Tue Jun 11 19:26:59 CEST 2019


> Em 11 de jun de 2019, à(s) 13:58:000, Jonas Frey <jf at probe-networks.de> escreveu:
> 
> 
>>> Run a open resolver and secure it propely
>> These two things are mutually exclusive. Sorry.
>> 
> 
> Well, then all of these (running open resolvers) must be wrong:
> - Google
> - Cloudflare
> - Quad9
> - OpenDNS
> - Yandex
> - Comodo
> - Norton
> - Clean Browsing
> - ...
> 
> 
> Anyway, isnt this the wrong discussion? The topic is wether RIPE should
> block, warn or pass these resolvers.
> 
> 


None of those organisations run authoritative servers on the same open recursive servers, either for direct or reverse domains. 



Rubens

Previous message (by thread): [dns-wg] NCC reverse delegation criteria
Next message (by thread): [dns-wg] NCC reverse delegation criteria

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]