Comment 20 for bug 1006743

I noticed the following on Ubuntu Precise:

hipdnsproxy gets started before NetworkManager manages to lift up the network connection using DHCP, so there is no usable nameserver in /etc/resolv.conf. This means that hipdnsproxy needs to install a script into /etc/resolvconf/update[-libc].d/ to get notified of changes to resolv.conf. And that script must take care not to end up in infinite recursion.

Also resolvconf normally stops processing the inputs once it hits the first nameserver entry that starts with 127., so if that is the line for hipdnsproxy, then we need to figure out the upstream nameserver in some other way. resolvconf cannot easily be told to dump the result anywhere else, so I think we should figure that out from resolvconf's inputs without involving resolvconf.

resolvconf works fine if you are either a provider of nameserver information, or a consumer, but being both is a bit tricky.