So I just tested again with the released image on Vagrant Atlas (https://atlas.hashicorp.com/ubuntu/boxes/xenial64/versions/20160914.0.0) and the image from Ubuntu Cloud Images (https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box) and the bug still remains. So the `/etc/resolv.conf` file is empty and no hosts can be resolved and thus not reached.
So I just tested again with the released image on Vagrant Atlas (https:/ /atlas. hashicorp. com/ubuntu/ boxes/xenial64/ versions/ 20160914. 0.0) and the image from Ubuntu Cloud Images (https:/ /cloud- images. ubuntu. com/xenial/ current/ xenial- server- cloudimg- amd64-vagrant. box) and the bug still remains. So the `/etc/resolv.conf` file is empty and no hosts can be resolved and thus not reached.