|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Message-ID: <9B66343BA96A5D4A9D6FBC00181A747D1B8679@exchange1> From: Chris Davis <chris.davis@computerjobs.com> To: "'nanog@merit.edu'" <nanog@merit.edu> Date: Mon, 19 Mar 2001 15:23:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Errors-To: owner-nanog-outgoing@merit.edu There is no problem in having hundreds or thousands of multiple root servers for DNS. We have a problem with CONTEXT. There is no existing way to ascertain the context from which users are resolving domain names. Solution: DNS Context Servers... DNS operators subscribe their machines to the DNS context they want. In one context, ".xxx" can resolve via new.net, in another context, ".xxx" resolves via one of the other .xxx providers. To keep ICANN and friends happy, ICANN could be the "default" context. Help calls then have one and only one additional question: "To which DNS context do you subscribe?" Context servers are pretty obviously where things are headed. Sooner or later, some new.net company is going to "take." If we already have DNS context servers in place, life will be much easier when an alternative TLD provider does succeed. -Chris Davis --not really selling private address space, that was a joke --not a fan of new.net's plugin, since it breaks ping, traceroute, and tradition
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |