commenting dns=dnsmasq out in the NetworkManager.conf leaves the
/etc/resolv.conf file intact.
I will test this on my other machines.
Unfortunately, the upgrade changed this setting to use dnsmasq.
It also is set in the default installation.
It solves my problem, thanks.
It creates another
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997076
Title:
network manager not in sync with DHCP and local resolv.conf
Wolf, you wrote:
settings that rely on any internal server names do not work.
You said that your (working) resolv.conf contains:
nameserver 10.1.0.4
nameserver 10.1.0.254
nameserver 195.202.128.3
Is it the case that the nameserver at 10.1.0.4 can resolve more names
than the nameserver at
Regarding this:
Network manager starts dnsmask with --no-resolv to ignore /etc/resolv.conf
That can be changed immediately to resolve this issue.
That is certainly not the right solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does it make any difference if you comment out dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997076
Title:
network manager not in sync with
Sorry Mathieu,
this behaviour might be correct from the dnsmask point of view. It does
not work from the system or users point of view.
Thunderbird and ssh do not resolv correctly (to name but two that my
users regularly use)
ping does not resolve correctly either. I have not even tried to find
This is expected behavior, as long as the DNS entries in /run/nm-dns-
dnsmasq.conf are correct. When that happens, please make sure dnsmasq is
indeed running (as otherwise you won't have anything listening on
127.0.0.1 to forward requests)
--
You received this bug notification because you are a
Would love to but currently things work as required. I have to wait till
problems emerge again.
My /etc/resolv.conf contains:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.1.0.4
Just had the error on another machine. /etc/resolv.conf contained:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search rsb.intern rsb.at
--
You received this bug
/run/nm-dns-dns-masq.conf
nameserver 10.1.0.4
nameserver 10.1.0.254
nameserver 195.202.128.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997076
Title:
network manager not in sync with DHCP and
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997076
Title:
network manager not in sync with DHCP and local resolv.conf
To manage notifications about this bug go to:
Please attach the contents of /run/nm-dns-dnsmasq.conf. That file should
contain exactly the information received from DHCP, and /etc/resolv.conf
should contain just 127.0.0.1 (thus pointing to dnsmasq); on a
standard vanilla Ubuntu install.
** Changed in: network-manager (Ubuntu)
Status:
12 matches
Mail list logo
