Ticket #10555 (closed defect: obsolete)
NAT DnsHostResolver reverse order of dns results compared to host
|Reported by:||ceztko||Owned by:|
|Version:||VirtualBox 4.1.14||Keywords:||nat dnshostresolver dns|
Because the host often needs to connect to a VPN with a local dns server, I enabled NAT DnsHostResolver (NAT DnsProxy wasn't enough) with the command:
VBoxManage.exe modifyvm <vmname> --natdnshostresolver1 on
It seemed to work correctly but I observed that DNS results order is reversed in a specific query I'm doing. Please note that the local dns server (192.168.101.20) is configured to answer in a specific order for this query (there's absolutely no round-robin, the result is always fixed). Host is Windows7 64-bit, guest is ubuntu 12.04 64 bit.
ping + nslookup in the host (correct, sidenote: dns server 192.168.101.20 is configured to serve to vpn users the public ip first for this specific host, and not the lan ip):
C:\Users\ceztko>ping hypervisor.rur.it-robotics.it Pinging hypervisor.rur.it-robotics.it [184.108.40.206] with 32 bytes of data: Control-C ^C C:\Users\ceztko>nslookup Default Server: lanmaster.it-robotics.it Address: 192.168.101.20 > hypervisor.rur.it-robotics.it Server: lanmaster.it-robotics.it Address: 192.168.101.20 Name: hypervisor.rur.it-robotics.it Addresses: 220.127.116.11 192.168.101.10
ping + nslookup in the guest (wrong, reversed):
ceztko@laptopbb:~$ ping hypervisor.rur.it-robotics.it PING hypervisor.rur.it-robotics.it (192.168.101.10) 56(84) bytes of data. ^C64 bytes from 192.168.101.10: icmp_req=1 ttl=63 time=70.1 ms --- hypervisor.rur.it-robotics.it ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 70.124/70.124/70.124/0.000 ms ceztko@laptopbb:~$ nslookup > hypervisor.rur.it-robotics.it Server: 10.0.2.3 Address: 10.0.2.3#53 Name: hypervisor.rur.it-robotics.it Address: 192.168.101.10 Name: hypervisor.rur.it-robotics.it Address: 18.104.22.168
Because, as stated in the manual, "the resolver mode will interpret the DNS requests and use the host's DNS API to query the information and return it to the guest", I'm expecting the guest to see the same order of the host for this query.