(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.