I've been duct-taping my way around this issue (and other similar issues) for years. It's terribly kludgy, but it's simple and effective and doesn't break on each upgrade:
/etc/init.d/openvpn start
while true ; do cp /etc/resolv.conf.good /etc/resolv.conf ; sleep 15 ; done
Or something like that, anyway. I actually run 'vpn up' and 'vpn down', but the above is how it deals with having too many cooks in the DNS kitchen.
I've been duct-taping my way around this issue (and other similar issues) for years. It's terribly kludgy, but it's simple and effective and doesn't break on each upgrade:
/etc/ init.d/ openvpn start conf.good /etc/resolv.conf ; sleep 15 ; done
while true ; do cp /etc/resolv.
Or something like that, anyway. I actually run 'vpn up' and 'vpn down', but the above is how it deals with having too many cooks in the DNS kitchen.