From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4142031A57A for ; Tue, 26 Aug 2025 18:16:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756232181; cv=none; b=C5GcYfFeFVkOXD45Z2Pum/r7f6u3LJKyFMB7KWmvc4S2aio9iT6bIyu8O653zL1HSntVYrxpgNUlWRIbLQB4utMWO9Ve8q3XFthbH9DDTEcHeLy377GlNqeu+OSrhRYTc0OV3HdLva+pqIz2UEL3at44kZf2IazFJngHLXtRsBw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756232181; c=relaxed/simple; bh=N1kMwO+oVeQAOyvycFjGPAnrwnf8RZ9lqy0SgyFrZeI=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=ZkSb0o3CU6aRBrjOWVW7sxq4/1UsQuDlOfEdmXC6OZufKAQN/M7Z7azpNKTmwI3N6oUaYYqgNzxF5VesSZ1ovzoPwRMmV5WDxOAfmvN4b0m2Vgk6o2xpbj1UKYXZBAWW4XN/TwTtKgPC4yxBGZIzF7AdLAqr1M/pQdsuzBCX08I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CgxHIQWY; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CgxHIQWY" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0D317C4CEF1; Tue, 26 Aug 2025 18:16:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1756232180; bh=N1kMwO+oVeQAOyvycFjGPAnrwnf8RZ9lqy0SgyFrZeI=; h=Date:Reply-To:Subject:To:Cc:References:From:In-Reply-To:From; b=CgxHIQWY/u56nr0YOBVaYrCx//VDbgF11AdCs5jScXNi2K7HoMueyg12ti5FAEw1d DsNKAvlzZqEsSYqbsp80fW0XJbehARYMVkf521Dv+xPFbjlwCtE2UsLdDarwL5JLTY F/4JK/5I0qaFWl15DCdkbMHsBpRIw3FB7cVmH7qx5fduNOrGFpV+2XVYwH1ppehsv+ lA/XjwXp1SGOqCVBsgW4YPPWKLz3NhS0ITLTQO2Pd1kfHAPaF3RjztGGjueXwUvjRx qpEgAQ5i7hXejqhiCyYwDVDfqy7Hu6jkTjnbFd+hzfjVYFK4E/ZePCaGptDOV5Ov4f /8o4FB68A+e2Q== Message-ID: <13a44d1d-2ed2-47b5-acc8-2b95e393b74b@kernel.org> Date: Tue, 26 Aug 2025 20:16:18 +0200 Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: Daniel Gomez Subject: Re: systemd-resolved and single-label DNS entries To: Jeff Layton , kdevops@lists.linux.dev Cc: chuck.lever@oracle.com References: <5a2d4ed91a7baf8487f37310c808bf615dcd834e.camel@kernel.org> Content-Language: en-US From: Daniel Gomez Organization: kernel.org In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 26/08/2025 16.21, Jeff Layton wrote: > On Tue, 2025-08-26 at 14:53 +0200, Daniel Gomez wrote: >> On 26/08/2025 12.58, Jeff Layton wrote: >>> I'm hitting a problem with NFS testing on kdevops guests. Recently when >>> I bring up a guest, it's unable to resolve the name of the NFS server >>> via DNS. >> >> FYI, nfstests works fine with Debian testing (forky). Both hosts and guests. >> >> > > > Thanks. Some questions: > > 1/ did your setup get the entries in /etc/hosts? That seems to be what No. AFAIK, we don't set up anything in the /etc/hosts. At least, the task below does not run during my bringup. - name: Fix up hostname on Debian guestfs hosts > has changed recently. That's not working for some reason. > > 2/ Does forky use systemd-resolved? The problem is clearly there with > Fedora 42. The DNS server on the virtual bridge works fine: It does not use systemd-resolved. At least, my system has been updated from trixie to forky and did not get that installed. > > ----------------8<----------------- > $ dig @192.168.122.1 kdevops-nfsd. > > ; <<>> DiG 9.18.33 <<>> @192.168.122.1 kdevops-nfsd. > ; (1 server found) > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24955 > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 1232 > ;; QUESTION SECTION: > ;kdevops-nfsd. IN A > > ;; ANSWER SECTION: > kdevops-nfsd. 0 IN A 192.168.122.85 > > ;; Query time: 0 msec > ;; SERVER: 192.168.122.1#53(192.168.122.1) (UDP) > ;; WHEN: Tue Aug 26 10:18:47 EDT 2025 > ;; MSG SIZE rcvd: 57 sudo virsh list --all | grep "dio\|interop\|posix\|iscsi\|nfsd" 13 debian13-interop running 14 debian13-nfsd running 15 debian13-dio running 16 debian13-posix running 17 debian13-iscsi running dig @192.168.122.1 debian13-nfsd ; <<>> DiG 9.20.11-4-Debian <<>> @192.168.122.1 debian13-nfsd ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4579 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;debian13-nfsd. IN A ;; ANSWER SECTION: debian13-nfsd. 0 IN A 192.168.122.193 ;; Query time: 0 msec ;; SERVER: 192.168.122.1#53(192.168.122.1) (UDP) ;; WHEN: Tue Aug 26 11:03:33 PDT 2025 ;; MSG SIZE rcvd: 58 > > $ resolvectl query kdevops-nfsd. > kdevops-nfsd.: 'kdevops-nfsd.' not found > ----------------8<----------------- dig debian13-nfsd ; <<>> DiG 9.20.11-4-Debian <<>> debian13-nfsd ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 60809 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;debian13-nfsd. IN A ;; Query time: 3 msec ;; SERVER: 192.168.64.5#53(192.168.64.5) (UDP) ;; WHEN: Tue Aug 26 11:09:44 PDT 2025 ;; MSG SIZE rcvd: 42 nslookup debian13-nfsd ;; Got SERVFAIL reply from 192.168.64.5, trying next server ;; Got SERVFAIL reply from 192.168.64.6 Server: 192.168.64.6 Address: 192.168.64.6#53 ** server can't find debian13-nfsd: SERVFAIL nslookup debian13-nfsd 192.168.122.1 Server: 192.168.122.1 Address: 192.168.122.1#53 Name: debian13-nfsd Address: 192.168.122.193 ;; communications error to 192.168.122.1#53: timed out ;; communications error to 192.168.122.1#53: timed out ;; communications error to 192.168.122.1#53: timed out ;; no servers could be reached > > It seems like we're doing something "unseemly" by putting bare names in > DNS like this, given that systemd-resolved won't pass them along. > > Since systemd-resolved will only resolve bare names without a domain > using LLMNR, we should either take steps to make that work, or fix it > so that systemd-resolved will forward the requests (by setting up a > proper domain name and setting up the search path in the resolver). >