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/[email protected]/
[cooperation-wg] DNS-based filtering
- Previous message (by thread): [cooperation-wg] DNS-based filtering
- Next message (by thread): [cooperation-wg] DNS-based filtering
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Sat Jan 25 10:42:18 CET 2014
On 25 Jan 2014, at 02:10, Michele Neylon - Blacknight <michele at blacknight.com> wrote: > Can you please provide examples of domains where the situation you described could exist? > > Eg: > "target domain name. In fact, for the sake of redundancy, a domain name may have many > authoritative servers, spread around the world and also operated by different companies." > > I can't see how that could work technically, but maybe I'm missing something - an example would be helpful Ever heard of zone transfer Michele? :-) Many organisations spread DNS service for their domains across multiple providers: avoiding single points of failure and all that. For instance many TLDs rely on a mixture of name servers they operate themselves, some provided by other TLD registries -- I'll slave your zone if you slave mine -- and others from commercial anycast providers. It might be true that the majority of registrants just stick with whatever DNS is offered by their registrar but not all of them do that. Clueful ones certainly don't.
- Previous message (by thread): [cooperation-wg] DNS-based filtering
- Next message (by thread): [cooperation-wg] DNS-based filtering
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]