Through NAT, DNS server pings but doesn't work

[Reinderien]

Version of VirtualBox: 4.3.6 r91406
Host: Windows 7 x64
Guest: Ubuntu 13.10 x64

I have two virtual adapters - the first is bridged to my wireless connection and traffic to it from the guest works fine.

The second is NAT to my VPN adapter. I had to write a set of routing table rules to tell Ubuntu when to route traffic to it:

Code: Select all

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 eth0
10.0.0.0        172.16.0.2      255.0.0.0       UG        0 0          0 eth1
...
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth1
172.16.0.0      0.0.0.0         255.240.0.0     U         0 0          0 eth1
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0

172.16 is the NAT in the guest (eth1), 10.0 is the NAT in the host, and 192.168 (eth0) is the wireless LAN in both places.

When I ping the address of the VPN's DNS server, it works completely fine. However, when I attempt this:

Code: Select all

nslookup vpn-specific-hostname ip-of-vpn-dns-server

I get this:

Code: Select all

;; connection timed out; no servers could be reached

Any idea how to fix this? Thanks...

[BillG]

I doubt that you will ever get that going. A VPN interface just doesn't have the necessary software.

[Reinderien]

I wonder what you mean by necessary software. It really seems to me like all of the necessary software is there, namely, a virtual VPN adapter in the host. Moreover, this whole setup was working perfectly until I rebooted the guest.

[noteirak]

until I rebooted the guest.

Sounds to me like you put in place some networking rule or configuration that got lost at reboot, but I don't see the link with Virtualbox from what you tell us.