[Touch-packages] [Bug 1690860] Re: systemd-resolved does not use DNS servers from DHCP
*** This bug is a duplicate of bug 1754671 *** https://bugs.launchpad.net/bugs/1754671 ** This bug has been marked a duplicate of bug 1754671 Full-tunnel VPN DNS leakage regression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1690860 Title: systemd-resolved does not use DNS servers from DHCP Status in systemd package in Ubuntu: Confirmed Bug description: Hi. I use Ubuntu 17.04 and I have systemd=232-21ubuntu3 installed. The problem is that it always uses 8.8.8.8 as DNS server. This is very disappointing because my mobile operator seems to block the server. And google knows nothing about my home dns zone, so I can't access my NAS by dns name. Here is a fragment from my /var/log/syslog upon connecting to network. I've switched systemd log level to debug. I see that dhcp4 receives correct DNS server (it works), but then systemd just ignores it and uses 8.8.8.8. May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Reject scan trigger since one is already pending May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5375] device (wlp1s0): supplicant interface state: ready -> inactive May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5432] policy: auto-activating connection 'AndroidGus' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5443] device (wlp1s0): Activation: starting connection 'AndroidGus' (ec68d7b6-b77e-4604-8981-40b56f017413) May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5473] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0] May 15 19:09:29 kibergus dhclient[24139]: receive_packet failed on wlp1s0: Network is down May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6530] device (wlp1s0): set-hw-addr: set-cloned MAC address to E4:A4:71:3C:4A:97 (permanent) May 15 19:09:29 kibergus kernel: [362356.079223] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6703] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6718] device (wlp1s0): Activation: (wifi) access point 'AndroidGus' has security, but secrets are required. May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6718] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6909] device (wlp1s0): state change: need-auth -> prepare (reason 'none') [60 40 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6912] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6914] device (wlp1s0): Activation: (wifi) connection 'AndroidGus' has security, and secrets exist. No new secrets needed. May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'ssid' value 'AndroidGus' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'scan_ssid' value '1' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'key_mgmt' value 'WPA-PSK' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'psk' value '' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7060] device (wlp1s0): supplicant interface state: inactive -> disconnected May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7068] sup-iface[0x55afd03050c0,wlp1s0]: config: set interface ap_scan to 1 May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7073] device (wlp1s0): supplicant interface state: disconnected -> inactive May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: SME: Trying to authenticate with d0:22:be:d3:7a:14 (SSID='AndroidGus' freq=2437 MHz) May 15 19:09:29 kibergus kernel: [362356.140572] wlp1s0: authenticate with d0:22:be:d3:7a:14 May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7260] device (wlp1s0): supplicant interface state: inactive -> authenticating May 15 19:09:29 kibergus kernel: [362356.147771] wlp1s0: send auth to d0:22:be:d3:7a:14 (try 1/3) May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Trying to associate with d0:22:be:d3:7a:14 (SSID='AndroidGus' freq=2437 MHz) May 15 19:09:29 kibergus kernel: [362356.155765] wlp1s0: authenticated May 15 19:09:29 kibergus kernel: [362356.156847] wlp1s0: associate with d0:22:be:d3:7a:14 (try 1/3) May 15 19:09:29 kibergus kernel: [362356.160692] wlp1s0: RX AssocResp from d0:22:be:d3:7a:14 (capab=0x411 status=0 aid=1) May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7394] device (wlp1s0): supplicant interface state: authenticating -> associating May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Associated with
[Touch-packages] [Bug 1690860] Re: systemd-resolved does not use DNS servers from DHCP
my syslog just says: syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: Positive Trust Anchors: syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test syslog:Aug 18 08:28:26 blacklab systemd-resolved[868]: Using system hostname 'blacklab'. ... network manager is getting the settings... ug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.0215] dhcp-init: Using DHCP client 'dhclient' Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.2092] dhcp4 (enx0050b6c88d96): activation: beginning transaction (timeout in 45 seconds) Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.3535] dhcp4 (enx0050b6c88d96): dhclient started with pid 2084 Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4079] dhcp4 (enx0050b6c88d96): address 172.25.5.48 Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4080] dhcp4 (enx0050b6c88d96): plen 24 (255.255.255.0) Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): classless static route 172.25.6.0/24 gw 172.25.5.6 Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): gateway 172.25.5.4 Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): lease time 86400 Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): nameserver '172.25.5.1' Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): nameserver '172.25.5.64' Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): domain name 'bsqt.homeip.net' Aug 18 08:28:27 blacklab NetworkManager[1098]: [1534595307.4081] dhcp4 (enx0050b6c88d96): state changed unknown -> bound Aug 18 08:28:29 blacklab NetworkManager[1098]: [1534595309.3017] dhcp6 (enx0050b6c88d96): activation: beginning transaction (timeout in 45 seconds) Aug 18 08:28:29 blacklab NetworkManager[1098]: [1534595309.3516] dhcp6 (enx0050b6c88d96): dhclient started with pid 2788 Aug 18 08:28:29 blacklab NetworkManager[1098]: [1534595309.7420] dhcp (enx0050b6c88d96): domain search 'test.example.com.' Aug 18 08:28:29 blacklab NetworkManager[1098]: [1534595309.7420] dhcp6 (enx0050b6c88d96): state changed unknown -> bound So it has gotten the DHCP and understood there are two nameservers available. blacklab% systemd-resolve status status: resolve call failed: No appropriate name servers or networks for name found blacklab% This has worked for fifteen years on my LAN. systemd is ignoring what it is getting from DHCP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1690860 Title: systemd-resolved does not use DNS servers from DHCP Status in systemd package in Ubuntu: Confirmed Bug description: Hi. I use Ubuntu 17.04 and I have systemd=232-21ubuntu3 installed. The problem is that it always uses 8.8.8.8 as DNS server. This is very disappointing because my mobile operator seems to block the server. And google knows nothing about my home dns zone, so I can't access my NAS by dns name. Here is a fragment from my /var/log/syslog upon connecting to network. I've switched systemd log level to debug. I see that dhcp4 receives correct DNS server (it works), but then systemd just ignores it and uses 8.8.8.8. May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Reject scan trigger since one is already pending May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5375] device (wlp1s0): supplicant interface state: ready -> inactive May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5432] policy: auto-activating connection 'AndroidGus' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5443] device (wlp1s0): Activation: starting connection 'AndroidGus' (ec68d7b6-b77e-4604-8981-40b56f017413) May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5473] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0] May 15 19:09:29 kibergus dhclient[24139]: receive_packet failed on wlp1s0: Network is down May 15 19:09:29 kibergus NetworkManager[6932]:
[Touch-packages] [Bug 1690860] Re: systemd-resolved does not use DNS servers from DHCP
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1690860 Title: systemd-resolved does not use DNS servers from DHCP Status in systemd package in Ubuntu: Confirmed Bug description: Hi. I use Ubuntu 17.04 and I have systemd=232-21ubuntu3 installed. The problem is that it always uses 8.8.8.8 as DNS server. This is very disappointing because my mobile operator seems to block the server. And google knows nothing about my home dns zone, so I can't access my NAS by dns name. Here is a fragment from my /var/log/syslog upon connecting to network. I've switched systemd log level to debug. I see that dhcp4 receives correct DNS server (it works), but then systemd just ignores it and uses 8.8.8.8. May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Reject scan trigger since one is already pending May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5375] device (wlp1s0): supplicant interface state: ready -> inactive May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5432] policy: auto-activating connection 'AndroidGus' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5443] device (wlp1s0): Activation: starting connection 'AndroidGus' (ec68d7b6-b77e-4604-8981-40b56f017413) May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.5473] device (wlp1s0): state change: disconnected -> prepare (reason 'none') [30 40 0] May 15 19:09:29 kibergus dhclient[24139]: receive_packet failed on wlp1s0: Network is down May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6530] device (wlp1s0): set-hw-addr: set-cloned MAC address to E4:A4:71:3C:4A:97 (permanent) May 15 19:09:29 kibergus kernel: [362356.079223] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6703] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6718] device (wlp1s0): Activation: (wifi) access point 'AndroidGus' has security, but secrets are required. May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6718] device (wlp1s0): state change: config -> need-auth (reason 'none') [50 60 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6909] device (wlp1s0): state change: need-auth -> prepare (reason 'none') [60 40 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6912] device (wlp1s0): state change: prepare -> config (reason 'none') [40 50 0] May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6914] device (wlp1s0): Activation: (wifi) connection 'AndroidGus' has security, and secrets exist. No new secrets needed. May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'ssid' value 'AndroidGus' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'scan_ssid' value '1' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'key_mgmt' value 'WPA-PSK' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.6915] Config: added 'psk' value '' May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7060] device (wlp1s0): supplicant interface state: inactive -> disconnected May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7068] sup-iface[0x55afd03050c0,wlp1s0]: config: set interface ap_scan to 1 May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7073] device (wlp1s0): supplicant interface state: disconnected -> inactive May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: SME: Trying to authenticate with d0:22:be:d3:7a:14 (SSID='AndroidGus' freq=2437 MHz) May 15 19:09:29 kibergus kernel: [362356.140572] wlp1s0: authenticate with d0:22:be:d3:7a:14 May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7260] device (wlp1s0): supplicant interface state: inactive -> authenticating May 15 19:09:29 kibergus kernel: [362356.147771] wlp1s0: send auth to d0:22:be:d3:7a:14 (try 1/3) May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Trying to associate with d0:22:be:d3:7a:14 (SSID='AndroidGus' freq=2437 MHz) May 15 19:09:29 kibergus kernel: [362356.155765] wlp1s0: authenticated May 15 19:09:29 kibergus kernel: [362356.156847] wlp1s0: associate with d0:22:be:d3:7a:14 (try 1/3) May 15 19:09:29 kibergus kernel: [362356.160692] wlp1s0: RX AssocResp from d0:22:be:d3:7a:14 (capab=0x411 status=0 aid=1) May 15 19:09:29 kibergus NetworkManager[6932]: [1494864569.7394] device (wlp1s0): supplicant interface state: authenticating -> associating May 15 19:09:29 kibergus wpa_supplicant[1151]: wlp1s0: Associated with d0:22:be:d3:7a:14 May 15 19:09:29 kibergus kernel:
