Ticket #3851 (closed defect: obsolete)

Opened 8 years ago

Last modified 21 months ago

DNS suffix not working when VirtualBox Host-Only Ethernet Adapter is active

Reported by: SkyBeam Owned by:
Priority: major Component: network
Version: VirtualBox 2.2.0 Keywords: host-only, DNS suffix, ipv6
Cc: Guest type: other
Host type: Windows

Description (last modified by frank) (diff)

I noticed that the VirtualBox Host-Only Ethernet Adapter is somehow screwing up correct DNS resolution on my hosts.

First I show you what happens before installing VirtualBox:

ipconfig /all shows the following for my Local Area Connection: ...

Connection-specific DNS Suffix . : mydomain.local


nslookup shows the following for a local server: C:\>nslookup server Server: server.mydomain.local Address:

Name: server.mydomain.local Addresses: xxxx:xxxx:xxxx:x::x

A ping to the host looks as follows: C:\>ping server

Pinging server.mydomain.local [xxxx:xxxx:xxxx:x::x] from xxxx:xxxx:xxxx:x:xxxx:xxxx:xxxx:xxxx with 32 bytes of data: Reply from xxxx:xxxx:xxxx:x::x: time<1ms ...

So the ping to the local server succeeds and uses the IPv6 address.

Now I install VirtualBox. As soon as the VirtualBox Host-Only Ethernet Adapter is installed the output of nslookup changes immediately:

C:\>nslookup server Server: server.mydomain.local Address:

Non-authoritative answer: Name: server Address:

The address returned corresponds to which is the re-direct page for non-existent domains used by my DNS provider (OpenDNS).

So it looks like the DNS suffix is not attached to the request any more and therefore DNS resolving fails locally. Manually adding the DNS suffix still works as expected (same output as without the VirtualBox Host-Only Ethernet Adapter).

But when I try to ping 'server' it gets a little strange: C:\>ping server

Pinging server [] with 32 bytes of data: Reply from bytes=32 time<1ms TTL=64 ...

So somehow it does not try to ping the IP resolved by OpenDNS ( but the local IP instead (which is not resolved by nslookup). The IPv6 address however is not used any more at all.

When I try to ping the full host name (server.mydomain.local) then it works perfectly. Also when I disable the VirtualBox Host-Only Ethernet Adapter within the network connections or the device manager and then either reboot or disable and re-enable my local Ethernet interface the problem disappears immediately and re-appears if I re-enable the Host-Only adapter. So there seems to be some problem with the DNS suffix when the VirtualBox Host-Only Ethernet Adapter is active.

I am running

  • Microsoft Windows Vista x64 Business
  • VirtualBox 2.2.0

Change History

comment:1 Changed 8 years ago by SkyBeam

I've found a work-around for this problem. It seems that Windows (at least Vista in my case) adds new network connections with higher priority than the existing on.e This causes the "VirtualBox Host-Only Network" connection to get higher priority than my already existing "Local Area Connection".

To change priorities follow this procedure:

  • Go to the control panel
  • Open "Network and Sharing Center"
  • Click on "Manage network connections"
  • Press left Alt-Key to open the menu bar
  • Open the "Advanced Menu"
  • Click on "Advances Settings..."
  • Confirm UAC prompt
  • In the dialog appearing move the "VirtualBox Host-Only Network" entry below your LAN connection
  • Click OK

This is a work-around and not really a solution. Probably the installer should be enhanced to set lower priority for the new network connection.

comment:2 Changed 21 months ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use