On 2020-09-01 01:18, Michael Catanzaro wrote:
On Mon, Aug 31, 2020 at 9:36 pm, Ed Greshko ed.greshko@greshko.com wrote:
But with that symlink it seems there is no integration with NetworkManager. So, if one has configured (which is the default) to acquire addresses automatically then DNS server info supplied by DHCP is ignored.
Is my take incorrect?
Hopefully. NetworkManager should be pushing DNS configuration from DHCP to systemd-resolved. Sounds like you might be encountering some strange bug....
OK, I looked a bit closer at the issue.
Indeed, systemd-resolved is getting the DNS server information. The actual issue is a lack of a DNS Domain. (a.k.a. "search" setting)
I don't think the DHCP server for the QEMU VMs is supplying a domain. However, Network Manager will add a "search" option to resolv.conf when "hostname" returns a FQDN.
This is using F33 Workstation.
[egreshko@f33g ~]$ hostname f33g.greshko.com
[egreshko@f33g ~]$ host nas Host nas not found: 2(SERVFAIL)
[egreshko@f33g ~]$ host nas.greshko.com nas.greshko.com has address 192.168.1.142 nas.greshko.com has IPv6 address 2001:b030:112f::19
[egreshko@f33g ~]$ resolvectl Global LLMNR setting: resolve MulticastDNS setting: resolve DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Fallback DNS Servers: 1.1.1.1 8.8.8.8 1.0.0.1 8.8.4.4 2606:4700:4700::1111 2001:4860:4860::8888 2606:4700:4700::1001 2001:4860:4860::8844
Link 2 (enp1s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.122.1 DNS Servers: 192.168.122.1 DNS Domain: ~.