This is the SBo for openresolv; (management framework for resolv.conf)
http://slackbuilds.org/repository/14...rch=openresolv
When using the update-resolv-conf for OpenVPN it pushes the DNS from the VPN server to the client, so that you are only using the DNS over the VPN tunnel...
When you make a connection to the OpenVPN server, resolvconf updates resolv.conf with the DNS from the VPN server, when you disconnect from the VPN, resolv.conf will now be empty. I thought dhcpcd would then update resolv.conf but it appears from this /path /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf the hook for dhcpcd is now to do all this through resolvconf.
So for now, maybe I have accomplished this by placing in resolvconf.conf;
name_servers=
Because now that nameserver stays listed in resolv.conf, along with the new updated one from the VPN, and when I disconnect from the VPN my nameserver still stays in resolv.conf
I just had to make sure that now with both my ISP nameserver and the VPN nameserver, I wasn't getting them both queried online, because the point here is to only use the VPN nameserver, and when I tested this online, I was getting that result.
So now I have either figured out the correct way of doing this with resolvconf, or placed a band-aid on it, this I am trying to still figure out, the correct approach to this.
Hope I've made this clear now...