[Pkg-utopia-maintainers] Bug#924002: network-manager: Only one search domain appears in resolv.conf, but there should be two from DHCP server
Will Berriss
will.berriss at gmail.com
Fri Mar 8 08:30:38 GMT 2019
Package: network-manager
Version: 1.6.2-3+deb9u2
Severity: important
After booting my computer I check in /etc/resolv.conf and see only one of
my search domain, namely the second one provided which is called white:
will at kodlix:~$ cat /etc/resolv.conf
# Generated by NetworkManager
search white
nameserver 10.187.204.3
nameserver 10.187.204.1
will at kodlix:~$
But I have two domains, blue and white, and my DHCP server sends these to
this computer.
I have found the following command fixes it temporarily:
root at kodlix:~# dhclient enp2s0
RTNETLINK answers: File exists
And now resolve.conf is correct:
root at kodlix:~# cat /etc/resolv.conf
search blue. white.
nameserver 10.187.204.3
nameserver 10.187.204.1
root at kodlix:~#
If I uninstall network-manager and setup /etc/network/interface with the
following contents:
# WPB
auto enp2s0
iface enp2s0 inet dhcp
and reboot I get the correct search line, i.e. both domains appear, blue
and white:
will at kodlix:~$ cat /etc/resolv.conf
search blue. white.
nameserver 10.187.204.3
nameserver 10.187.204.1
will at kodlix:~$
I now get both domains, albeit with a . on the end, but things work now.
By the way, all the other clients on my network get the correct search
domains blue and white
in that order, so the dhcp server config is correct. (These other clients
are raspbian stretch computers
and Windows 10 computers, and I checked my mobile phone DHCP values too.)
Finally, I see the following in /var/log/syslog, in case that helps:
Mar 7 21:49:24 kodlix NetworkManager[423]: <info> [1551995364.8466] dhcp
(enp2s0): domain search 'blue.'
Mar 7 21:49:24 kodlix avahi-daemon[425]: New relevant interface
enp2s0.IPv4 for mDNS.
Mar 7 21:49:24 kodlix NetworkManager[423]: <info> [1551995364.8466] dhcp
(enp2s0): domain search 'white.'
It's as if the second domain search entry simply replaces the first one.
So for now I have uninstalled network-manager and just rely on
/etc/network/interface which works ok as shown above.
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.115
ii dbus 1.10.26-0+deb9u1
ii init-system-helpers 1.48
ii libaudit1 1:2.6.7-2
ii libbluetooth3 5.43-2+deb9u1
ii libc6 2.24-11+deb9u4
ii libglib2.0-0 2.50.3-2
ii libgnutls30 3.5.8-5+deb9u4
ii libgudev-1.0-0 230-3
ii libjansson4 2.9-1
ii libmm-glib0 1.6.4-1
ii libndp0 1.6-1+b1
ii libnewt0.52 0.52.19-1+b1
ii libnl-3-200 3.2.27-2
ii libnm0 1.6.2-3+deb9u2
ii libpam-systemd 232-25+deb9u9
ii libpolkit-agent-1-0 0.105-18+deb9u1
ii libpolkit-gobject-1-0 0.105-18+deb9u1
ii libreadline7 7.0-3
ii libselinux1 2.6-3+b3
ii libsoup2.4-1 2.56.0-2+deb9u2
ii libsystemd0 232-25+deb9u9
ii libteamdctl0 1.26-1+b1
ii libuuid1 2.29.2-1+deb9u1
ii lsb-base 9.20161125
ii policykit-1 0.105-18+deb9u1
ii udev 232-25+deb9u9
ii wpasupplicant 2:2.4-1+deb9u2
Versions of packages network-manager recommends:
ii crda 3.18-1
ii dnsmasq-base 2.76-5+deb9u2
ii iptables 1.6.0+snapshot20161117-6
ii iputils-arping 3:20161105-1
ii isc-dhcp-client 4.3.5-3+deb9u1
ii modemmanager 1.6.4-1
ii ppp 2.4.7-1+4
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-utopia-maintainers/attachments/20190308/814c1f92/attachment.html>
More information about the Pkg-utopia-maintainers
mailing list