From: Daniel Gomez <da.gomez@kernel.org>
To: Jeff Layton <jlayton@kernel.org>, kdevops@lists.linux.dev
Cc: chuck.lever@oracle.com
Subject: Re: systemd-resolved and single-label DNS entries
Date: Tue, 26 Aug 2025 14:53:13 +0200 [thread overview]
Message-ID: <f9150bde-7530-42ba-8ffa-e37b2c7c345b@kernel.org> (raw)
In-Reply-To: <5a2d4ed91a7baf8487f37310c808bf615dcd834e.camel@kernel.org>
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.
next prev parent reply other threads:[~2025-08-26 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 10:58 systemd-resolved and single-label DNS entries Jeff Layton
2025-08-26 12:53 ` Daniel Gomez [this message]
2025-08-26 14:21 ` Jeff Layton
2025-08-26 15:07 ` Chuck Lever
2025-08-26 15:49 ` Jeff Layton
2025-08-26 16:32 ` Jeff Layton
2025-08-26 19:04 ` Daniel Gomez
2025-08-27 13:25 ` Jeff Layton
2025-08-26 18:16 ` Daniel Gomez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9150bde-7530-42ba-8ffa-e37b2c7c345b@kernel.org \
--to=da.gomez@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox