Date: Wed, 14 Aug 2024 16:53:19 -0700 From: Bakul Shah <bakul@iitbombay.org> To: Alex Arslan <ararslan@comcast.net> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Diagnosing virtual machine network issues Message-ID: <9BD08D66-B95C-4551-A005-12218CF18FD2@iitbombay.org> In-Reply-To: <08AA87E3-D631-4EA1-AA30-37B4709630CB@comcast.net> References: <202408141829.47EITc7B080532@gndrsh.dnsmgr.net> <08AA87E3-D631-4EA1-AA30-37B4709630CB@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 14, 2024, at 4:38=E2=80=AFPM, Alex Arslan <ararslan@comcast.net> = wrote: >=20 > 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? 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9BD08D66-B95C-4551-A005-12218CF18FD2>