You make some good points Charles, but I find the following to be most
So if I owned example.com, I'd have three name servers (assuming I delegate
authority to the sub-domains):
- for example.com (ns1.example.com)
- for east.example.com (ns2.east.example.com)
- for west.example.com (ns3.west.example.com)
Those who register domain names such as "example.com" have public
hosting providers and a public name server providers as opposed to
using a DNS registry on one's internal networks to define subdomains.
So, rather than your suggestion of having a 1-to-1 mapping between a
domain name and a DNS server on one's private network and calling that
a "subdomain", the public provider will use "A" records to define
subdomains (map west.example.com, and east.example.com to any public
IP address of one's choosing including the option of mapping both
subdomain names to the same IP address).
This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact