Quote:
Originally Posted by pixellany
Ummm---I think that this is a convention and not part of any fundamental protocol. i.e. the servers could just as well be named fred.domain.com, and nancy.domain.com
Is there not also a thing called subdomains--such that if an IP maps to "domain.com", that one can still address "subdomain1.domain.com" and "subdomain2...." etc.??
|
You are absolutely correct. It is in fact a naming convention and has nothing to do with the functionality of DNS. In the example of ns1.domain.com, ns1 is simply a subdomain of domain.com. If you had linux.rocks.the.house.domain.com, then linux would be a subdomain of rocks, which is a subdomain of the which is a subdomain of house wich is a subdomain of 'domain' which is technically a subdomain of .com, or the top level domain.