About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [dns-wg] Deprecation of ip6.int scheduled for 1 June 2006

  • To: Alexander Gall gall@localhost
  • From: Bernhard Schmidt berni@localhost
  • Date: Wed, 15 Mar 2006 17:27:05 +0100
  • Cc: bmanning@localhost, Doug Barton dougb@localhost, dns-wg@localhost

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






 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community