Re: Diagnosing virtual machine network issues

> On Aug 2, 2024, at 5:58 PM, Bakul Shah <bakul@iitbombay.org> wrote:
> 
> On Aug 2, 2024, at 3:52 PM, Alex Arslan <ararslan@comcast.net> wrote:
>> 
>>> Just a comment and a name server line:
>>> 
>>> $ cat /etc/resolv.conf
>>> # Generated by resolvconf
>>> nameserver 192.168.122.1
>> 
>> I believe that is the host IP, so I guess the VM is using the host for DNS
>> resolution? Interestingly, if I add `nameserver 8.8.8.8` below the line
>> with the host IP, it takes 10 seconds rather than 30 to reach the expected
>> domain resolution failure. If I put 8.8.8.8 above the host IP, the domain
>> resolution failure is instantaneous.
> 
> What does your host use as a namesever?

The nameserver is 127.0.0.53. It sets options edns0 and trust-ad, and
includes a search entry as well.

> 
>> Not a particularly satisfying conclusion to this saga as I don't understand
>> why it's happening but at least I have a workaround that should hopefully
>> do the job. I really appreciate everyone's help and input thus far!
>> 
>> What's the best way to add `nameserver 8.8.8.8` to /etc/resolv.conf as
>> part of the VM's configuration?
> 
> You should diagnose the problem of the nameserver at 192.168.122.1
> and fix it to act properly. I don't use vm (just bhyve) so can't help
> you with its config.

I do still plan to try to figure out what the actual issue is, but I also
now have a path forward in the meantime. :)