Network connect makes changes directly to the /etc/resolv.conf file. This causes issues with the newer way that Ubuntu does DNS resolutions which is to point DNS to the local resolver/cacher: dnsmasq. Once NC disconnects and you change networks, eg go from office to home then DNS stops working correctly. What happens is that NC deletes the /etc/resolv.conf file which is actually symlinked to /run/resolvconf/resolv.conf. Whats worse is that NC actually deletes the original file not the link. So when you try to restore the file with:
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
It fails as /run/resolvconf/resolv.conf is now gone. re-installing resolvconf does not fix it and neither does running resolvconf. So the best way I have found so far is to first backup /run/resolvconf/resolv.conf to another location. After you disconnect NC I then run a script that removes /etc/resolv.conf, replaces the deleted /run/resolvconf/resolv.conf and then links it's back to /etc again.
Does anyone know a way to avoid this or do I pretty much have he best "fix" in place already? Any way to prevent NC from breaking it in the first place.
Oh how I wish Juniper would sort their issues out. Juniper has been notoriously HORRIBLE on Linux and 64bit especially for over 4 years now.