[Bug 1158732] New: NetworkManager configuration problem
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1158732 Bug ID: 1158732 Summary: NetworkManager configuration problem Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: comes@naic.edu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have a problem with the following setup and NetworkManager: I have bind running locally. I set in /etc/sysconfig/network/config: NETCONFIG_DNS_FORWARDER="bind" and run: netconfig update In this way /etc/resolv.conf contains: nameserver 127.0.0.1 However, while this is enough when I use wicked, with MetworkManager things are different. NetworkManager adds to /etc/resolv.conf the DNS server list it gets from the DHCP server. To avoid this I add dns=none in the main section of NetworkManager.conf. This setup was working in 15.0: the command netconfig update would write the appropriate resolv.conf and NetworkManager would not change it. However in 15.1 this does not work anymore. The reason is that now /etc/resolv.conf is a link to /var/run/netconfig/resolv.conf so while the command 'netconfig update' would write the appropriate resolv.conf in /var/run/netconfig, after a reboot if the command 'netconfig update' is not executed, /var/run/netconfig/resolv.conf does not exist. The solution would be to put in NetworkManager.conf: dns=none rc-manager=netconfig but this doesn't work because dns=none forces rc-manager=unmanaged Right now the workaround I'm using is to put this line in /etc/init.d/boot.local: if [[ -h /etc/resolv.conf && ! -f /etc/resolv.conf ]]; then netconfig update ; fi I think that NetworkManager forcing rc-manager=unmanaged when dns=none is a bug. It should force it only if there is no explicit setting of the rc-manager parameter. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com