Date: Wed, 14 Aug 2024 21:41:29 -0700 From: Alex Arslan <ararslan@comcast.net> To: Bakul Shah <bakul@iitbombay.org> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Diagnosing virtual machine network issues Message-ID: <9F3F65F2-0695-434A-B4A1-9C614FD7F9AA@comcast.net> In-Reply-To: <9BD08D66-B95C-4551-A005-12218CF18FD2@iitbombay.org> References: <202408141829.47EITc7B080532@gndrsh.dnsmgr.net> <08AA87E3-D631-4EA1-AA30-37B4709630CB@comcast.net> <9BD08D66-B95C-4551-A005-12218CF18FD2@iitbombay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 14, 2024, at 4:53 PM, Bakul Shah <bakul@iitbombay.org> wrote: > > On Aug 14, 2024, at 4:38 PM, Alex Arslan <ararslan@comcast.net> wrote: >> >> In the VM, /etc/resolv.conf has the host IP by default > > > /etc/resolv.conf should always point to a dns server. Is the > host running a DNS service? If it is, it should respond pretty > quickly for a nonexistent hostname query. Why doesn't it? > If it is not running a DNS service, how did you arrive at this > decision to point to the host? I didn't set it explicitly, it's what got configured automatically with `sysrc ifconfig_DEFAULT=SYNCDHCP`. I'm unsure whether the host is running a DNS service, and to be honest I don't know how to tell. `resolvectl` on the host says the current DNS server is 8.8.8.8. It also lists 1.1.1.1 as an available server, as well as 4.4.4.4 as a fallback. > You may want to run tcpdump on the host and at the same time > on a linux VM and see what happens. You can do the same thing > for a freebsd VM to try to narrow down where the problem lies. I actually did that exactly a while back at the suggestion of someone on this mailing list, and I posted the results to the thread: https://lists.freebsd.org/archives/freebsd-hackers/2024-July/003409.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F3F65F2-0695-434A-B4A1-9C614FD7F9AA>