Adding additional DNS servers via NetworkManager config - also has 0
effect on `systemd-resolve --status`
DNS Domains are changed, though.
Here is systemd-resolve --status:
Global
DNS Servers: 8.8.8.8
8.8.4.4
2001:4860:4860::8888
2001:4860:4860::8844
DNS Domain: ***.lan
***.com
***.prod
***.grid
***.com
Here is the contents of /var/lib/dhcp/dhclient.leases:
lease {
interface "wlp3s0";
fixed-address 172.29.232.71;
option subnet-mask 255.255.255.0;
option routers 172.29.232.1;
option dhcp-lease-time 14400;
option dhcp-message-type 5;
option domain-name-servers 172.29.156.110,172.31.11.233,172.31.11.235;
option dhcp-server-identifier 172.29.156.110;
option domain-search "***.lan.", "***.com.", "***.prod.", "***.grid.",
"***.com.";
option dhcp-renewal-time 7200;
option dhcp-rebinding-time 12600;
option domain-name "***.lan";
renew 3 2017/05/03 15:55:39;
rebind 3 2017/05/03 15:55:39;
expire 3 2017/05/03 15:55:39;
}
lease {
interface "wlp3s0";
fixed-address 172.29.232.71;
option subnet-mask 255.255.255.0;
option routers 172.29.232.1;
option dhcp-lease-time 300;
option dhcp-message-type 5;
option domain-name-servers 172.29.156.110,172.31.11.233,172.31.11.235;
option dhcp-server-identifier 172.29.156.110;
option domain-search "***.lan.", "***.com.", "***.prod.", "***.grid.",
"***.com.";
option dhcp-renewal-time 150;
option dhcp-rebinding-time 259;
option domain-name "***.lan";
renew 3 2017/05/03 15:58:08;
rebind 3 2017/05/03 16:00:08;
expire 3 2017/05/03 16:00:49;
}
lease {
interface "wlp3s0";
fixed-address 172.29.232.71;
option subnet-mask 255.255.255.0;
option routers 172.29.232.1;
option dhcp-lease-time 14400;
option dhcp-message-type 5;
option domain-name-servers 172.29.156.110,172.31.11.233,172.31.11.235;
option dhcp-server-identifier 172.29.156.110;
option domain-search "***.lan.", "***.com.", "***.prod.", "***.grid.",
"***.com.";
option dhcp-renewal-time 7200;
option dhcp-rebinding-time 12600;
option domain-name "***.lan";
renew 3 2017/05/03 17:41:59;
rebind 3 2017/05/03 19:28:08;
expire 3 2017/05/03 19:58:08;
}
Here is the contents of the network manager config file:
cat /etc/NetworkManager/system-connections/CORP
[connection]
id=CORP
type=wifi
interface-name=wlp3s0
permissions=
secondaries=
timestamp=1493827494
[wifi]
mac-address=
mac-address-blacklist=
mac-address-randomization=0
mode=infrastructure
seen-bssids=
ssid=CORP
[wifi-security]
group=
key-mgmt=wpa-eap
pairwise=
proto=
[802-1x]
altsubject-matches=
ca-cert=/usr/local/share/ca-certificates/ROOTCA-SUBCA/ROOT.cer
eap=peap;
identity=
password-flags=1
phase2-altsubject-matches=
phase2-auth=mschapv2
[ipv4]
dns=172.29.156.110;172.31.11.233;172.31.11.235;
dns-search=
method=auto
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
ip6-privacy=0
method=auto
--
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/1688032
Title:
systemd-resolved DHCP: does not change DNS servers
Status in systemd package in Ubuntu:
New
Bug description:
When I connect to Corporate WiFi(Enterprise PEAP with certificate,
MSCHAPv2) and acquire a DHCP lease, the DNS servers are never changed
by systemd-resolved from Google's servers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688032/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
