VirtualBox

Opened 4 years ago

Last modified 4 years ago

#18932 new defect

No DNS from DHCP on NAT connection

Reported by: Han Fastolfe Owned by:
Component: network/NAT Version: VirtualBox 6.0.12
Keywords: DNS DHCP Cc:
Guest type: all Host type: Windows

Description

On VirtualBox 6.0.12, with plain NAT configuration, the domain name resolution does not work anymore on Windows/Linux guests on Windows host.

I've checked quite everything on host and guests configuration and come up to the hypothesis that VirtualBox dhcp "server" does not send the DNS address, but it used to do on previous versions.

This is confirmed by DHCP not containing the DNS entry as shown by the following DHCP response:

$ sudo nmap --script broadcast-dhcp-discover

Starting Nmap 7.60 at 2019-09-12 08:08 CEST
Pre-scan script results:
| broadcast-dhcp-discover:
|   Response 1 of 1:
|     IP Offered: 10.0.2.16
|     DHCP Message Type: DHCPOFFER
|     Subnet Mask: 255.255.255.0
|     Router: 10.0.2.2
|     IP Address Lease Time: 1d00h00m00s
|_    Server Identifier: 10.0.2.2
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.51 seconds

Change History (2)

comment:1 by Han Fastolfe, 4 years ago

As a workaround the DNS must be set manually in IPV4 configuration on each VM.

comment:2 by Valery Ushakov, 4 years ago

Please, provide the log from the VM (as we ask to in the bug submission guidelines).

Also, please, provide the contents of the host's /etc/resolv.conf.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use