New WAN, Private TLD

[Kevin Darcy]

Each company would have to run their own DNS server or use someone else's
DNS server that has knowledge of both Internet names and names in the private
TLD. At the very least, these "special" DNS servers would need to have a
"stub" definition for the TLD, and then somebody would have to host the
TLD zone itself and all of the company.TLD zones delegated beneath it. Add
slaves if you care about redundancy.

Having dealt with a "private internet" setup before (the ANX), I'll warn you
that your biggest challenge probably isn't DNS; it's email. Very few people
want to change their email addresses, so you end up making your mail servers
bend over backwards rewriting foo.com addresses into foo.TLD addresses. Blech.


- Kevin

Erik Tamminga wrote:

> Hi,
>
> We're about to link numerous companies into a private WAN. For naming
> devices in this WAN we would like to use our own private TLD (all ip's are
> rfc1918, private ip's, 10.x.x.x). For example server1.company1.our_tld. All
> companies should then be able to resolve this name.
>
> Is this easy to do or should we think of some other solution? We'd have to
> keep in mind that some or all companies have a internet connection and might
> be using an ISP's dns server as their default, my guess is that this would
> have to change.
>
> Are there any documents discussing these kind of dns design topics?
>
> Erik