EDIT: I was editing the resolv.conf file via: sudo nano /etc/resolv.conf 
from:
# Generated by NetworkManager
nameserver 10.0.2.3

TO
# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 8.8.4.4

Saving the settings and then the commands work just fine:

Sorin@centos7 /  $ host google.com
google.com has address 172.217.19.110
google.com has IPv6 address 2a00:1450:400d:809::200e
google.com mail is handled by 20 alt1.aspmx.l.google.com.
google.com mail is handled by 10 aspmx.l.google.com.
google.com mail is handled by 40 alt3.aspmx.l.google.com.
google.com mail is handled by 30 alt2.aspmx.l.google.com.
google.com mail is handled by 50 alt4.aspmx.l.google.com.

However, I have to do this everytime I am ssh-ing into vagrant cause the 
changes won't save. Any idea why is that?

Thanks



On Wednesday, 7 August 2019 12:18:04 UTC+3, Devils Kiddo wrote:
>
> This is what I got:
>
> Sorin@centos7 ~  $ host -v google.com
> Trying "google.com"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20567
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;google.com.                    IN      A
>
> ;; ANSWER SECTION:
> google.com.             3600    IN      A       216.58.214.206
>
> Received 44 bytes from 10.0.2.3#53 in 19 ms
> Trying "google.com"
> Received 28 bytes from 10.0.2.3#53 in 0 ms
> Trying "google.com"
> Host google.com not found: 3(NXDOMAIN)
> Received 28 bytes from 10.0.2.3#53 in 0 ms
> Trying "google.com"
> Received 28 bytes from 10.0.2.3#53 in 0 ms
> Trying "google.com"
> Host google.com not found: 3(NXDOMAIN)
> Received 28 bytes from 10.0.2.3#53 in 0 ms
>
> Previously I was editing the hosts file but not sure if I remember the 
> command to edit it right: sudo nano /etc/hosts
> If that was it  is looking different now
> I was replacing the resolvers in there with the Google one's (8.8.8.8 and 
> 8.8.4.4) and it was working just fine
>
>
> On Wednesday, 7 August 2019 12:01:13 UTC+3, Jim McGinness wrote:
>>
>> Try using "host -v google.com" to get some additional information. 
>> There's nothing special about the vagrant install - the guest system is 
>> going to rely on the dhcp response (or whatever network configuration 
>> you've specified) to locate a DNS resolver. I suppose some resolvers 
>> provide only limited lookup services.
>>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/387be75a-0134-48eb-8e27-5bae7c479945%40googlegroups.com.

Reply via email to