Open shurick81 opened 5 years ago
I run vagrant destroy --force; vagrant up
a few times with the same result on this host. Then I also tried another stack on contrib: https://github.com/SubPointSolutions/uplift-contrib/blob/c6c4304aa1678c73e6386ae255e19ee2f4bdde03/uplift-vagrant/dc16-client/Vagrantfile and it also ended up with the same error.
On my other host it worked just fine. The difference I noticed is that on the host where it works properly, DNS server is available via 192.168.16.5:
PS C:\Windows\system32> nslookup
Default Server: UnKnown
Address: 10.0.2.3
> server 192.168.16.5
Default Server: [192.168.16.5]
Address: 192.168.16.5
> uplift.local
Server: [192.168.16.5]
Address: 192.168.16.5
Name: uplift.local
Addresses: 192.168.16.5
10.0.2.15
But as you can see in initial post, the same DNS lookups fails. It might be kind of faulty host configuration, firewall or something but I have other dc-client stacks (not uplift) working on it, so I need to dig deeper to figure out the issue.
I stumbled into this issue now when I try uplift on a laptop that I have never used uplift on before: https://gist.github.com/shurick81/435f6559509536b3fb5d2426691a867c.
On the host:
Running from this vagrant directory: https://github.com/SubPointSolutions/uplift-contrib/tree/130a98e581ca4db1530b7e355cc43b37cd86e331/uplift-vagrant/crm-dev.
On the dc VM:
On the crm VM:
Is it normal that the default DNS server on the crm machine is 10.0.2.3? is it any known issue that you could notice in CI @avishnyakov?