Ticket #5789 (closed defect: invalid)
UseHostResolver not working for Linux guest on Windows XP host
|Reported by:||alusiani||Owned by:|
UseHostResolver is not working for me both with VirtualBox 3.1.0 and 3.1.2 for Linux guests on a Windows XP host. The Windows XP account used for running VirtualBox is *unprivileged*. I setup a Centos 5.4 guest and a Slitaz guest on Windows XP as mentioned in the manual. Although the manual is not clear enough, by reading the web and the log files it appears that for UseHostResolver to work DNSProxy should be zero. Therefore I configured as follows:
VBoxManage setextradata "Linux Guest" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/UseHostResolver" 1 VBoxManage setextradata "Linux Guest" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/DNSProxy" 0
I tried also "!DNSProxy 1" and it did not work either.
Both Linux guests are configured to either set DNS from DHCP or set it statically to 10.0.2.3 and end up with 10.0.2.3 in /etc/resolv.conf. I use NAT networking plus one hostonly interface in the default subnet to communicate between host and guest. Attempting DNS resolution from the guest with "host" or "nslookup" commands hangs. By forcing the DNS server to other addresses like 10.0.2.2 or 10.0.2.14 I the host/nslookup command ends with an error, while with DSN server = 10.0.2.3 it hangs. The same commands work if the VM is rebooted after configuration with "DNSProxy 1" and "UseHostResolver 0".
I report a probably unrelated issue. With the mentioned configuration I can connect from the guest to the host using the hostonly address at 192.168.56.1 but also at other addresses which were unexpected for me: 10.0.2.2, 10.0.2.3, 10.0.2.4. I have an ssh server on the host, I am able to login on the host from the guest at all the above addresses, the only thing that changes is that for the ssh server on the host the connection appear to come from "localhost" for the 10.* addressed and from the hostonly guest IP in the other case.