DNS test flaky #2313
Description
I some times see the DNS integration test fail:
<vm> Resolved IP address of www.facebook.com with DNS server 10.0.2.3: 31.13.72.36
<vm> some_address_that_doesnt_exist.com couldn't be resolved
<vm> Resolved IP address of doubleclick.net with DNS server 10.0.2.3: 142.250.74.142
<vm> Resolved IP address of googlesyndication.com with DNS server 10.0.2.3: 216.58.211.4
<vm> Resolved IP address of google-analytics.com with DNS server 10.0.2.3: 142.250.74.4
<vm> Resolved IP address of github.com with DNS server 4.2.2.1: 140.82.121.4
<vm> Error occurred when resolving IP address of theguardian.com with DNS server 4.2.2.1: Request timed out
<vm> qemu-system-x86_64: terminating on signal 15 from pid 588669 (/nix/store/8w718rm43x7z73xhw9d6vh8s4snrq67h-python3-3.12.10/bin/python3)
[ TIMEOUT ] vmrunner timed out after 20 seconds
👷⛔ Step 7.3 failed (nix-shell --pure --arg withCcache true --argstr unikernel ./test/net/integration/dns/ --run ./test.py)
On the previous run all the addresses were resolved.
I think the right approach here is to bring up a small non-IncludeOS dns server together with this test and not depend on an external DNS server. I think having the external resolves is a nice test to run manually, so I think we should keep the functionality, but as opt-in.