Well, that solution have a problem not present in vanilla
DNS -- nameservers no longer correspond to administrative
boundaries.
And it does not do anything to fix the name collision problem.
--vadim
From nanog-owner@merit.edu Mon Apr 22 19:26 PDT 1996
Return-Path: <nanog-owner@merit.edu>
Received: from postman.ncube.com by butler.ncube.com (5.0/SMI-SVR4)
id AA16645; Mon, 22 Apr 1996 19:26:03 +0800
Received: from titan.sprintlink.net by postman.ncube.com (4.1/SMI-4.1)
id AA28280; Mon, 22 Apr 96 19:27:42 PDT
Received: from merit.edu (merit.edu [35.1.1.42]) by titan.sprintlink.net (8.6.9/8.6.9) with ESMTP id WAA01557 for <avg@titan.sprintlink.net>; Mon, 22 Apr 1996 22:27:31 -0400
Received: (from daemon@localhost) by merit.edu (8.7.5/merit-2.0) id VAA29036 for nanog-outgoing; Mon, 22 Apr 1996 21:38:51 -0400 (EDT)
Received: from chops.icp.net (chops.icp.net [199.0.55.71]) by merit.edu (8.7.5/merit-2.0) with ESMTP id VAA29030 for <nanog@merit.edu>; Mon, 22 Apr 1996 21:38:48 -0400 (EDT)
Received: by chops.icp.net id <20637>; Mon, 22 Apr 1996 21:38:40 +0100