FS#54555 - [dhclient] Unable to set resolver from resolv.conf; startup continuing but DDNS support may be ...
Attached to Project:
Arch Linux
Opened by Stefan (steinwanderer) - Friday, 23 June 2017, 05:51 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 19:05 GMT
Opened by Stefan (steinwanderer) - Friday, 23 June 2017, 05:51 GMT
Last edited by Balló György (City-busz) - Thursday, 08 June 2023, 19:05 GMT
|
Details
Description:
I have a wierd error with dhclient together with NetworkManager. This happens only, when "dhcp-send-hostname" is set to "yes", which is needed for my router: $ journalctl --no-hostname --no-pager --full --priority=warning --boot|grep dhc Jun 23 06:23:56 dhclient[939]: irs_resconf_load failed: 59. Jun 23 06:23:56 dhclient[939]: Unable to set resolver from resolv.conf; startup continuing but DDNS support may be affected Jun 23 06:23:58 dhclient[1033]: irs_resconf_load failed: 59. Jun 23 06:23:58 dhclient[1033]: Unable to set resolver from resolv.conf; startup continuing but DDNS support may be affected Additional info: $ nmcli connection show Kabelgebundene\ Verbindung\ 1 |grep hostname ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: thinkpad-x200 ipv6.dhcp-send-hostname: yes ipv6.dhcp-hostname: thinkpad-x200.fritz.box * package version(s) dhclient 4.3.5-1 networkmanager 1.8.0-1 network-manager-applet 1.8.2-1 libnm 1.8.0-1 libnm-glib 1.8.0-1 networkmanager-openvpn 1.2.10-1 networkmanager-pptp 1.2.4-2 networkmanager-vpnc 1.2.4-2 nm-connection-editor 1.8.2-1 Steps to reproduce: Set the option to send the hostname and the hostname itself with nmcli and reboot. The above error will show up in the journal. ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: myhostname ipv6.dhcp-send-hostname: yes ipv6.dhcp-hostname: myhostname.mydomain If "send-hostname" is set to "no" again, the error disappears. (after two reboots, this is the wierd part.) ipv4.dhcp-send-hostname: no ipv6.dhcp-send-hostname: no |
This task depends upon
For some strange reason the following line apears in /etc/resov.conf, which imho cause the error:
nameserver fe80::12fe:edff:fec8:4ca3%enp0s25
The added "%<interface_name>" is most likely the problem here.