Re: detecting resolv.conf changes

[Roy Marples <roy marples name>]

Howard Chu wrote:
> Understood. At any rate, it works for me; I run by own build from git
> with this patch (plus the no-scanning-while-connected patch). (It's far
> better than what I used to have to do, rewriting BIND's forwarders.conf
> file on every interface change and restarting it. And using a laptop
> without a local caching nameserver is just a bad idea, particularly when
> you're using a GSM modem and every byte costs 1.5cents.)

NM supports resolvconf.
My implementation (openresolv) can write out configuration files for
BIND, dnsmasq and PowerDNS Recursor. With dnsmasq and DBus, the local
resolver is never restarted with is even better :)

If we can get NM to call resolvconf with each the original resolv.conf
for each interface instead of a single merged instance then resolvconf
can make a better informed decision about how to configure these
resolvers. I'm not sure how difficult that would be though, or even if
desirable from a NM perspective.

Thanks

Roy

[1] http://roy.marples.name/projects/openresolv