generic/debian boxes have fixed DNS servers when used in Vagrant with libvirt

[h4-l5]

generic/debian boxes have fixed DNS servers when used in Vagrant with libvirt

[ladar]

It's been awhile since I tried using the DNS servers provided over DHCP. I can recall at least two issues:

Some of the box configs would fail to build because a locallly provided DNS servers might respond with an IPv6 addresses, even though the host/guest didn't support v6. As I recall the Ubuntu installers on Hyper-V were particularly fragile.

The second issue was some of the unit tests I run on the Magma version of the boxes require a DNS server to be conformant when handling specific scenarios, like a domain name being invalid. And sometimes DNS servers would violate these rules. For example a consumer ISP might redirect any invalid DNS names to its own servers. This caused spurious test failures.

All that being said, I've slowly been migrating newer box configs over to only using the hardcoded servers as a fall back. If I haven't already, we can try updating the Debian 11/12 configs to start with and see what breaks.

[h4-l5]

And I just noticed that the workaround is not sufficient if you're trying to use synced folders of type nfs instead of rsync.

The setup process tries to install the necessary NFS client packages but fails because the download servers cannot be resolved. This happens before the bootstrap script gets started.

[h4-l5]

Oh, I forgot to add version information. All of the boxes were version 4.2.16, pulled via Vagrantfile.

[ekohl]

Isn't this a duplicate of #54?