Previously working NAT network no longer has DNS
Posted: 28. Mar 2017, 16:42
I use VirtualBox in one of my classes and most students are doing fine with it. The students all have the same host system: HP Z Book laptops running windows 10.
However, I now have one students with a problem that we have not been able to solve. All of his guest machines (which are all versions of Debian Linux) can no longer resolve DNS lookups. The host is still able to resolve DNS just fine. We can also ping both internal and external IPs just fine (ping 8.8.8.8 works, ping google.com does not). The student has been successfully using these virtual appliances the entire semester until now. It seems the networking broke some time around March 20th. We found several windows updates that had installed on the 20th and tried uninstalling those but to no avail.
I've found MANY forum posts about DNS issues and have tried a plethora of things suggested by those posts:
- Hard-coding google's name servers into resolve.conf and /etc/network/interfaces
- Double checking and opening up windows firewall
- Uninstalling recent windows updates
- Uninstalling and re-installing virtual box from scratch
- Throwing the laptop out the window ... (didn't help)
We DESPERATELY need to get him back in working order and are looking for any ideas or workaround (however severe) to get this solved!
Here's how the virtual machines are setup:
Seth B.
However, I now have one students with a problem that we have not been able to solve. All of his guest machines (which are all versions of Debian Linux) can no longer resolve DNS lookups. The host is still able to resolve DNS just fine. We can also ping both internal and external IPs just fine (ping 8.8.8.8 works, ping google.com does not). The student has been successfully using these virtual appliances the entire semester until now. It seems the networking broke some time around March 20th. We found several windows updates that had installed on the 20th and tried uninstalling those but to no avail.
I've found MANY forum posts about DNS issues and have tried a plethora of things suggested by those posts:
- Hard-coding google's name servers into resolve.conf and /etc/network/interfaces
- Double checking and opening up windows firewall
- Uninstalling recent windows updates
- Uninstalling and re-installing virtual box from scratch
- Throwing the laptop out the window ... (didn't help)
We DESPERATELY need to get him back in working order and are looking for any ideas or workaround (however severe) to get this solved!
Here's how the virtual machines are setup:
Any help or debugging ideas are greatly appreciated!!Host OS: Windows 10
Guest OS: Debian Jessie (Turnkey Linux LAMP and Node.js servers)
Networking: eth0 = NAT, eth1 = Host Only Networking (note, only eth0 has problems, eth1 works fine)
Default options everywhere else
Seth B.