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/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Sun Feb 27 11:33:37 CET 2005
Nils Ketelsen wrote: > And now the next question: If a ccTLD NS gets a /32, why shouldn't a > Authoratitative NS for a real big number of Domains (of a domain hoster, for > example) get a /32? What is the difference between a ccTLD Nameserver and > any other authoritative NS? just as a side note: it's not the number of domains/zones that matters here. In the case of a multi-zone server they are not forced to serve all zones from a single name or IP address, i.e. they can achieve resilience and load distribution by other means. Some problems may still be similar, though. -Peter
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]