> I'm sort of confused, and maybe someones seen this.
> If I run a cacheing dns server somewhere on my private
> internal lan (10.x.x.x), then, by definition, it's not
> authoriative for my zone and just cache's query responses
> it gets back, correct?
>
> If you guys run a cacheing dns server
> Hi Folks,
>
> I'm sort of confused, and maybe someones seen this.
> If I run a cacheing dns server somewhere on my private
> internal lan (10.x.x.x), then, by definition, it's not
> authoriative for my zone and just cache's query responses
> it gets back, correct?
Right.
> If you guys run a
Charles Steinkuehler wrote:
>
> > I'm sort of confused, and maybe someones seen this.
> > If I run a cacheing dns server somewhere on my private
> > internal lan (10.x.x.x), then, by definition, it's not
> > authoriative for my zone and just cache's query responses
> > it gets back, correct?
>
> Richard,
>
> Thanks for the reply. I was hoping to find a method
> where I didn't have to run a master DNS, though tinydns
> sounds like the best solution.
>
> I'm not sure one could run it on their LRP without paying
> extra to Wacbell.
>
> But a cacheing dns server that could somehow be
> How does it get back 10.1.2.2, if the dnscache is not
> authoritative for it's zone, but rather it just caches
> answers it gets from the net, and it can't ever get
> the correct answer for 10.1.2.2 from the net
>
> These requests lead to dns timeouts and LAN delays.
>
> It's important for w
> > Dnscache+tinydns can be configured to do exactly what you
> > describe. Bind
> > dnscache to the internal interface of your LRP box and
> > configure your
> > internal hosts to use it as their DNS server. Bind tinydns
> > to localhost
> > (127.0.0.1) on the LRP box and load it with information
