Bare metal with Ubuntu-18.04-server behind a NAT

Get it, but these two solution can not work with 'vagrant up installer'.
The vm Installer uses nfs type to set synced_folder and the vm will install nfs client before the vm.provision shell scripts runs. That's to say the vm still use the wrong nameserver 127.0.0.53.

The issue is with VM's to be created during Vagrant up or Vagrant up installer

Solution 1:
#!/bin/bashset -e
echo "nameserver %{NATIP}" >> /etc/resolv.conf
Solution 2: Could be https://gerrit.onap.org/r/c/multicloud/k8s/+/99540/2/kud/hosting_providers/vagrant/node.sh#87 adding this information inside Vagrantfile (https://github.com/onap/multicloud-k8s/blob/master/kud/hosting_providers/vagrant/Vagrantfile) instead of node.sh. 

r.kuralamudhan: The broader question should be why aren't the 18.04 VMs getting created properly in my opinion. Solution 1 & 2 could be a potential fix. However, this could be perceived as hardcoding the values inside the VM rather than debugging why aren't the VMs getting created fine with the correct nameserver information in the first place.

Another patch may fix the issues:
https://gerrit.onap.org/r/c/multicloud/k8s/+/99540/2/kud/hosting_providers/vagrant/node.sh#87

To solve it, you can add a shell script to Vagrantfile to set the name server manually.

#!/bin/bash
set -e
echo "nameserver %{NATIP}" >> /etc/resolv.conf

Some of the errors it caused:
Stderr from the command:

W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic/InRelease Temporary failure resolving 'us.archive.ubuntu.c om'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Temporary failure resolving 'us.archive. ubuntu.com'
W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease Temporary failure resolving 'us.archiv e.ubuntu.com'