Bob Vincent
2018-10-15 14:03:57 UTC
I've submitted an Ubuntu bug-report here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797602
*Problem*:
- systemd breaks resolvconf-dependent DNS
*Test case:*
- Install dnsmasq with systemd.
*Result*:
- The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the
make_resolv_conf() function to pass DHCP information to the
/sbin/resolvconf program.
- The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the
make_resolv_conf() function to write DHCP information to
/run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf
- As a result, resolvconf never runs, and dnsmasq never receives the
DHCP-supplied nameservers.
- Therefore, DNS resolution is broken.
*Expected result*:
- DHCP-supplied nameservers should be passed to both resolvconf and to
systemd.
*Workaround*:
- Use the 127.0.0.53 address for the systemd resolver as the dnsmasq
upstream server.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797602
*Problem*:
- systemd breaks resolvconf-dependent DNS
*Test case:*
- Install dnsmasq with systemd.
*Result*:
- The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the
make_resolv_conf() function to pass DHCP information to the
/sbin/resolvconf program.
- The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the
make_resolv_conf() function to write DHCP information to
/run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf
- As a result, resolvconf never runs, and dnsmasq never receives the
DHCP-supplied nameservers.
- Therefore, DNS resolution is broken.
*Expected result*:
- DHCP-supplied nameservers should be passed to both resolvconf and to
systemd.
*Workaround*:
- Use the 127.0.0.53 address for the systemd resolver as the dnsmasq
upstream server.
--
The web is like usenet, but
the elephants are untrained.
The web is like usenet, but
the elephants are untrained.