Re: The state of resolv.conf

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2008-09-17 at 08:29 -0500, Les Mikesell wrote:
> Simo Sorce wrote:
> > > 
> >> So the answer seems to be that glibc will not change it's simple
> >> internal resolver (which has more limitations than just noticing
> >> resolv.conf changes), but the recommendation is that lwresd or a local
> >> caching nameserver be used for more complex DNS setups.
> > 
> > A caching nameserver that can be instructed what to do when conditions
> > change is what we really need.
> 
> Isn't it a little late to redesign the internet so names and addressing 
> aren't delegated hierarchically?

What would this mean ?

But let me ask a question in your own style: do you understand the
difference between a normal DNS server and a local cache ?

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux