The state of resolv.conf

Ahmed Kamal email.ahmedkamal at
Tue Sep 16 11:34:06 UTC 2008

Is there any current daemon that does this effect of directing name
resolution to specific servers according to IP ranges and/or domain names,
with the option of adding/removing servers on the fly ? Does dnsmasq do that

On Tue, Sep 16, 2008 at 1:19 PM, Nils Philippsen <nils at> wrote:

> On Tue, 2008-09-16 at 11:05 +0100, Paul Howarth wrote:
> > Another problem with modifying resolv.conf is that most processes only
> > read it once, usually shortly after starting up, so any changes that
> > happen after that don't get picked up by existing processes. So for
> > instance you could have a web browser that couldn't resolve names from a
> > VPN tunnel that had been brought up after the browser had been started.
> Which is a bug IMO. If applications don't use the glibc supplied
> functions for name-resolving, they should at least reinvent the wheel
> properly and check for changes to resolv.conf.
> Nils
> --
> Nils Philippsen      "Those who would give up Essential Liberty to purchase
> Red Hat               a little Temporary Safety, deserve neither Liberty
> nils at       nor Safety."  --  Benjamin Franklin, 1759
> PGP fingerprint:      C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011
> --
> fedora-devel-list mailing list
> fedora-devel-list at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fedora-devel-list mailing list