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]/
[dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
- Previous message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
- Next message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bernhard Schmidt
berni at birkenwald.de
Wed Mar 15 17:27:05 CET 2006
Alexander Gall wrote: > Removing ip6.int is fine, keeping broken zones is not. Full ACK. Most IPv6 setups I've done so far have an empty zone configured in the resolvers for ip6.int (and did not request a delegation in ip6.int for their own block), because having no reverse name immediately is much more convenient than having no reverse name after a mandatory break waiting for the various delegation errors to timeout. ip6.int hasn't been stable for years, but the situation has become nearly unbearable since the ip6.int zones are no longer maintained. Not all hosts can be configured/updated to do ip6.arpa only (Cisco routers :-) ). I'm really looking forward to get ip6.int removed forever. Regards, Bernhard
- Previous message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
- Next message (by thread): [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]