Hosting multiple TLDs

[Barry Margolin]

In article <biitit$2scq$1 at sf1.isc.org>,
Jonathan de Boyne Pollard  <J.deBoynePollard at tesco.net> wrote:
>That is _good_ practice.  _Best_ practice is for all of the intermediate
>domain names to be subdomains of the domain being delegated itself.  (For
>example, all of the intermediate domain names used in the delegation of
>"gwu.edu." would be subdomains of "gwu.edu." itself.)

While that may be nice, it's highly impractical in many cases.  Don't
forget another best practice: having nameservers with few common points of
failure.  Many organizations implement this getting slave DNS service from
their ISP or some other third party.  The slave DNS provider's servers are
virtually never in the customer's domain, and often not even in the same
TLD (if they're an ISP they're likely to have a .NET domain).

Many organizations don't even host their own master DNS, they outsource it
completely.  Do you really expect ISP's and other DNS providers to have
servers in every potential TLD?

-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.