I'm seeing a similar issue on current Ubuntu Yakkety with Android phone AP via WPA2-personal:
$ systemd-resolve www.guugle.com
www.guugle.com: 208.73.210.200 208.73.210.214 208.73.211.178 208.73.210.217
-- Information acquired via protocol DNS in 13.6889s.
-- Data is authenticated: no
`host www.guugle.com` and nslookup on the other hand return immediately during this time. Disabling DNSSEC and restarting systemd-resolved using the instructions above has no effect (the above trace is after disabling).
syslog contains the lines:
Oct 31 20:25:41 xxxxx systemd-resolved[5309]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.0.1.
resolv.conf contains only `nameserver 127.0.0.1`. The problem disappears if I add also the line `nameserver 192.168.43.1` (that's the upstream DNS) --- however, the following line appears in the logs:
Oct 31 20:34:05 xxxxx systemd-resolved[5309]: Using degraded feature set (UDP) for DNS server 192.168.43.1.
I'm seeing a similar issue on current Ubuntu Yakkety with Android phone AP via WPA2-personal:
$ systemd-resolve www.guugle.com
208.73. 210.214
208.73. 211.178
208.73. 210.217
www.guugle.com: 208.73.210.200
-- Information acquired via protocol DNS in 13.6889s.
-- Data is authenticated: no
`host www.guugle.com` and nslookup on the other hand return immediately during this time. Disabling DNSSEC and restarting systemd-resolved using the instructions above has no effect (the above trace is after disabling).
syslog contains the lines:
Oct 31 20:25:41 xxxxx systemd- resolved[ 5309]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.0.1.
resolv.conf contains only `nameserver 127.0.0.1`. The problem disappears if I add also the line `nameserver 192.168.43.1` (that's the upstream DNS) --- however, the following line appears in the logs:
Oct 31 20:34:05 xxxxx systemd- resolved[ 5309]: Using degraded feature set (UDP) for DNS server 192.168.43.1.