On 22-jul-04, at 11:46, Gert Doering wrote:
In fact, it would probably be a good idea to keep ip6.int around forever. If nobody uses it, there is no harm in it being there. If people still use it, then removing it causes problems.
Maintaining both trees does cause quite some administrative overhead (depending on the name server software and zone file format you use, you cannot just point both zones to the same file.
Then you probably also use an OS that doesn't support file system links? :-) The way I understand it, it's even possible to use the dname mechanism to fix all of this, so this argument isn't all that convincing. But even if:
Even if you can, the whole thing falls apart if you want to delegate a /48 to your customer, and the customer has only ip6.arpa, but not ip6.int -> lame delegation, or distinct zone files further up the tree).
I'm not arguing EVERYONE should continue to support ip6.int forever, just that the delegations to those who still do should remain in place. If you feel you shouldn't support ip6.int in your network, by all means, remove it.