Ticket #17584 (closed defect: fixed)

Opened 2 years ago

Last modified 22 months ago

DNS server IP not propagated to guest VM in NAT mode -> fixed in 5.2.10

Reported by: DaveU8282 Owned by:
Component: network/NAT Version: VirtualBox 5.2.6
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by vushakov) (diff)

In a Linux host's /etc/resolv.conf, it is possible to define an entry representing a DNS server running on the local host:


In this case, a VirtualBox VM with a virtual network interface in NAT mode will see an IP in the NAT network provided in place of, thus making it possible for the VM to use the host's local DNS server. For instance, if is assigned to the VirtualBox host and is assigned to the guest, the guest would see in the DNS resolver list.

However, an equivalent construct:


which also represents the local Linux host, is not correctly handled by VirtualBox NAT. In this case, the VM will see in the DNS server list which is not NATted to the host. This results in a broken DNS resolver entry. If there is no other nameserver in the resolver list, DNS lookups will fail, or if there are additional nameservers in the list, DNS lookups will be delayed due to the lame DNS server entry.

This has been observed with a Windows 10 guest but it's expected that other guests would see the same issue.

Proposed solution: handle exactly like by NATting it to the NAT IP for the Linux host.

Change History

comment:1 Changed 2 years ago by vushakov

  • Description modified (diff)

Thanks for the report.

comment:2 Changed 22 months ago by michael

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from DNS server IP not propagated to guest VM in NAT mode to DNS server IP not propagated to guest VM in NAT mode -> fixed in 5.2.10
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use