Distributed DNS ?

[Hz]

Hi Kevin,

I am more refering your first paragragh of assumption.

Our current WAN environment has got many satalite sites bound to it by just
some serial link dedicated lines. If the router at either end goes down, or
if the line goes down, all the TCP/IP services within such satelite site
(those servers sit within their office premises, ie. within the same LAN
segment) will not be able to function since the well-known names cannot be
resolve. Our DNS servers is currently situated at strategic locations, what
I see as more like a hub.

What I'll like to achieve is - our satelite sites will still be able to run
all their TCP/IP service as far as the local servers are concern. I
understand that during such unschedule downtime, it would be impossible to
access any extranet resouces unless our solution is to have some stand-by
link implemented. I am starting to look into cheap and easy to implement
solution. I talk to someone, an MCSE (yes u are correct), before and he
actually mentioned about the Cache Domain Name Directory. This, according to
him, can be piggy back on the local offices' existing NT server and would
not take up too much of its resources. But then, I am not limiting myself to
only a Microzofic solution.

Regards,



DNS Administration <dnsadm at daimlerchrysler.com> wrote in message
news:3855A2C4.536F271F at daimlerchrysler.com...
> Hz wrote:
>
> > Hi,
> >
> > I am interested in searching for an economic solution of implementing a
> > localized DNS. Some kind of fault tolerrance when our WAN link goes
down.
>
> It's hard to come up with a solution when you haven't described hardly
> anything about the problem. What happens today when your WAN link goes
down?
> Is everyone internally suddenly unable to resolve names even in your own
> domain? That would probably be because you are relying on your ISP to
> provide internal as well as external name service. To fix this, you'd need
> to set up an internal DNS server of your own on your side of the WAN.
>
> Or, are your users just unable to resolve Internet names when your WAN
link
> goes down? There's not a lot that can be done about that, but how much
does
> it really matter? Since the users can't get to the sites anyway, the fact
> that they can't even resolve the names just adds a little insult to
injury.
> You could run a caching-only server if you want, in which case some of the
> names would still be resolvable for a while. Apart from the redundancy
> aspect, there are also performance benefits to running a caching-only
> nameserver.
>
> Without more to go on, it's hard to get into any specifics.
>
> > ANybody ever heard of a Cache Domain Name Directory before?
>
> Nope. Is that a product name? A Microsoftized name for a caching-only
> nameserver configuration, perhaps?
>
>
> - Kevin
>
>
>