http://bugzilla.suse.com/show_bug.cgi?id=1092352 http://bugzilla.suse.com/show_bug.cgi?id=1092352#c35 --- Comment #35 from Frank Kruger <fkrueger@mailbox.org> --- (In reply to Jonathan Kang from comment #33)

(In reply to Marius Tomaschewski from comment #30)

...

This issue is nothing new and will persist as long as NetworkManager continues to sometimes break the policies and write the files directly instead to use netconfig.

I see. I'll propose a patch to NM fixing this. Make NetworkManager force update /etc/resolv.conf using netconfig when netconfig exits with code 20.

One question about this. NetworkManager spawns

...

/sbin/netconfig modify --service NetworkManager and writes INTERFACE='NetworkManager' DNSSEARCH='abc' DNSSERVERS='xyz' to netconfig. To force update /etc/resolv.conf using netconfig, should NetworkManager spawn /sbin/netconfig modify -f --service NetworkManager and write related information to netconfig?

...

You can call "netconfig update -f" to enforce to update the files:

And for anyone who is having this issue, run "netconfig update -f" to update /etc/resolv.conf. You won't encounter this issue any more.

Is this for granted? I vaguely remember that when the issue appeared in Tumbleweed some users reported in the factory mailing list that “netconfig update -f“ did not solve the problem. -- You are receiving this mail because: You are on the CC list for the bug.