Re: Classes other then IN

On Mon, Oct 5, 2009 at 2:53 PM, Erwin Hoffmann <[email protected]> wrote:
> Hm.  Does this really help ?

Two disadvantages I can think of:

  1. It means stub resolver code and (even more significantly)
application code probably have to be updated to allow the user to
specify whether foo.com should be looked up in CLASS=IN, CLASS=CN,
CLASS=FR, ....

  2. Because NS records only specify a name for a name server and not
a class, if I own foo.com in CLASS=CN and I want to use Big DNS Corp
for my DNS hosting, I can't delegate my domain to them unless they
also own a domain name in CLASS=CN.

I think a simpler solution than using CLASS=CN to designate a query
that originates at China's name servers would be for caches to get
.cn's name server information from somewhere other than ICANN's root
zone file.  E.g., similar to how dnscache already allows you to
configure root/servers/cn with a list of IP addresses, and then ICANN
has no control over names within the .cn namespace.

This is no more difficult to implement than supporting CLASS=CN (in
either case you need a way to distribute and maintain a small list of
IP addresses for each country), and it has the benefit of not
requiring applications to be modified and being backwards compatible
with the current system (at least until China and ICANN get into a
disagreement).