On Wed, Jan 11, 2012 at 12:07:20PM -0500, Avri Doria wrote:
- wouldn't he be looking for support of these new Classes in addition to Class IN, not instead?
Then he has to change the basic assumption of RFC 1034 first: The database for any class is organized, delegated, and maintained separately from all other classes. Since, by convention, the name spaces are the same for all classes, the separate classes can be thought of as an array of parallel namespace trees. [...] Within a class, "cuts" in the name space can be made between any two adjacent nodes. After all cuts are made, each group of connected name space is a separate zone. The zone is said to be authoritative for all names in the connected region. Note that the "cuts" in the name space may be in different places for different classes, the name servers may be different, etc.
- doesn't this break because DNS Alias records pay no attention to Class and therefore aliased names would collide despite being in different classes?
CNAME processing is defined within a the same class as the queried class. In this way it's class independent, simply it's part of the algorithm, not part of the retured data. Same goes for NS, DS, etc. Because the databases are requried to be separate, a CNAME in one class can't influence an other one.