Internal and External DNS

[Kevin Darcy]

The main problems I see are:

1. Maintenance. You'd have to keep your internal root in sync with the
Internet root zone.

2. Collisions. What if multiple organizations want the name "mail" or
"ftp"?

3. Inefficiency. Most resolvers will tack on a "default" domain or go
through a searchlist before querying a single-label name as is. This
wastes resources and increases query latency. It also means that your
root-zone names need to be *globally*unique*, otherwise "mail", for
instance, will get obscured by "mail.hq.example.com" for those clients
having a default domain of "hq.example.com".


- Kevin

Lorne.Evans at gems1.gov.bc.ca wrote:

>    Hi:
>
>     Continuing the discussion:
>     If I were to consider the following configuration "a private root
> for my internal DNS - running with an edited 'additions to' the
> internic root zone file to give external access to all TLD's - and all
> internal NS's having root servers pointing to solely the private root
> servers" - what would be the issues - if any - to having NO TLD for
> my "special zone" of private resources -  I.E. - one very large flat
> namespace root zone file for "special" names?  I.E. the fqdn of server1
> instead of server.mydomain?  For Internet access and mail - I would
> have the standard delegated xxx.ca et al zones in my EXTERNAL DNS.
>
>    Thanks!
>
>    - Lorne.
>
> In article <93lg7k$o9u at pub3.rc.vix.com>,
>   Kevin Darcy <kcd at daimlerchrysler.com> wrote:
> >
> > It might be a good idea to avoid some of the gTLD's which ICANN has
> announced
> > it will implement (.aero, .biz, .coop, .info, .museum, .name
> and .pro).
> > Otherwise, you may have problems communicating with nodes in those
> domains, if
> > and when they are actually implemented.
> >
> > - Kevin
> >
> > bind at timmy.ws wrote:
> >
> > > On 11 Jan 2001 09:00:37 -0800, "MJL" <no at thanks.com> wrote:
> > >
> > > >I've been looking around the internet (probably in the wrong
> places) and
> > > >haven't found an answer for this yet.
> > > >
> > > >We are running an internal ".com" domain on our servers.  Our
> external DNS
> > > >is currently hosted by our ISP and will sometime come in house.
> This
> > > >obviously is a problem because both severs are authoritative for
> our domain
> > > >so we can't make real lookups to the outside.
> > > >
> > > >We are going to change our internal DNS but are unsure what to use
> as a
> > > >domain extension.  I have seem people use ".lan" or ".cxm", etc.
> Is there
> > > >any sort of standard or even a most commonly used extension for
> this
> > > >situation.
> > > >
> > > >Thanks for any help
> > > >
> > > >Matthew Lowrance
> > > >Positronic Industries Inc.
> > >
> > > I use ".int", for internal, but according to appendix 3 in "DNS and
> > > BIND", .int is a TLD for "International". You can basically use
> > > whatever you want. ".lan" sounds great, I might have to steal that
> one
> > > from you!! You can use .foo, .bogus, .shit, whatever you
> > > really want. I don't know of any industry standard.
> > >
> > > >
> > > >
> > > >
> > > >
> > > >
> >
> >
>
> Sent via Deja.com
> http://www.deja.com/