Comment # 5 on bug 960153 from Jonathan Kang

(In reply to Ludwig Nussel from comment #4)
> Unfortunately, that is not how it works in openSUSE. We have netconfig,
> NetworkManager is meant to to provide the information to netconfig which in
> turn takes the necessary steps to update e.g. /etc/resolv.conf. I guess some
> patch got lost that detects use of netconfig?

Ah. You are right.

(In reply to Jan Kara from comment #0)
> Created attachment 660275 [details]
> My /etc/sysconfig/network/config file
> 
> I'm using Networkmanager to manage my network connection including updating
> /etc/resolv.conf (since this is a laptop which I connect at different
> places). As I need to use openvpn to connect to SUSE internal network, I'm
> using dnsmasq to forward resolving of SUSE domain names to SUSE name servers
> and the rest is resolved through the local name server. This used to work
> fine with 13.2.
> 
> Now I have updated to 42.1 and my resolv.conf contains:
> # Generated by NetworkManager
> search suse.cz suse.de
> nameserver 192.168.2.1
> 
> When 'netconfig update' is run, it complains that resolv.conf has been
> updated manually and so it won't touch it. I have to run 'netconfig update
> -f' to force updating /etc/resolv.conf and then my DNS setup starts working
> again.
> 
> So apparently some cooperation between NetworkManager and netconfig has been
> broken with 42.1...

Try adding "rc-manager=netconfig" in the main section of NetworkManager.conf
to see if it fixes this problem.