Network manager doesn't honor configuration for dns
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| network-manager (Ubuntu) |
Low
|
Unassigned |
Bug Description
Hello,
i've recently created a new ubuntu vm machine starting from xubuntu 17.10.
after disabling systemd-resolve i configured my wired connection to use my dns server on 127.0.0.1 and 9.9.9.9 as backup however network-manager is rewriting /etc/resolv.conf with the right search path but with the wrong nameserver (127.0.1.1) .
this is my /etc/NetworkMan
#####
[main]
plugins=
[ifupdown]
managed=false
[device]
wifi.scan-
#####
This is the config of the interface
# nmcli device show eth0
GENERAL.DEVICE: eth0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 08:00:27:88:A7:A4
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: Wired connection 1
GENERAL.CON-PATH: /org/freedeskto
WIRED-PROPERTIE
IP4.ADDRESS[1]: 10.0.2.15/24
IP4.GATEWAY: 10.0.2.2
IP4.DNS[1]: 127.0.0.1
IP4.DNS[2]: 9.9.9.9
IP6.ADDRESS[1]: fe80::144b:
IP6.GATEWAY: --
This is my resolv.conf
cat /etc/resolv.conf
# Generated by NetworkManager
search nl.europe.intranet europe.intranet
nameserver 127.0.1.1
As workaround i have fixed /etc/resolv.conf and chattr +i it but i think network manager should honor my conf .
that wired connection is set up as dhcp address only.
Btw that dnsmasq running on 127.0.0.1 is my configured dnsmasq not the one network managers used to use a long time ago:
ps auxwww| grep dnsm
dnsmasq 1764 0.0 0.0 57420 2828 ? S 11:20 0:00 /usr/sbin/dnsmasq -x /run/dnsmasq/
root 4022 0.0 0.0 14356 972 pts/1 S+ 11:32 0:00 grep --color=auto dnsm
Sebastien Bacher (seb128) wrote : | #1 |
Changed in network-manager (Ubuntu): | |
importance: | Undecided → Low |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.