kmweber wrote:
glg wrote:
kmweber wrote:
It's "valid" in the sense that "it'll probably work," but not in the sense that "it fits in with the conceptual, hierarchical view of the domain name system."
Seriously? Just stop. You're making yourself look like a fool. Using the same IP for both a domain and a subdomain is not a "massive misuse" of DNS, nor will it "probably work", it does work, just fine. In fact, it works just fine to have hundreds of domains and hundreds more subdomains pointing to the same IP.
Please respond to what I actually said, and not what you might like to pretend I said. I never denied that what you describe would "work" in a technical sense. What I
am saying is that having a subdomain and its parent domain resolve to an address at all, regardless of whether or not they're the same, is not valid regardless of whether or not it works, because it's inconsistent with the conceptual framework of the domain name system, period.
I sense that you might be thinking of the restriction on certain types of RRs, which do not allow them to be at the same level; an example is a zone with an SOA record which also has a CNAME for @. That will work in today's DNS (and many companies take advantage of it), but is technically a violation of
RFC1912 (see ยง2.4). I can't think of any standards recommendation for what you are describing here.
The hierarchical nature of the DNS that you refer to really means zone delegation, and not names within that zone. Although this may have been a guiding principle at some point in the past -- the DNS existed before I became interested in IT -- it is not today as implemented. I can probably find hundreds of zones which have an A for @ and subdomains within them.
I won't argue with you and tell you that you're wrong, just that everybody doing so is likely taken aback by what can be considered an odd belief. The Web would be broken indeed if the DNS did not allow folks to type "google.com" instead of "www.google.com".
FAQ
Search
Members
Register
Login [ Anonymous ]
Whatever you say, bucko. As someone else stated, things should just fail if a user types linode.com instead of