NAT Network - DHCP problem: no DNS

[petardo]

Postby petardo » 17. Nov 2013, 03:20 I am using the "NAT NETWORK" Network Adapter. I have found a DHCP SERVER problem: IF

• DHCP SERVER is enabled in the file / preferences / network / nat network section,
• and NAT NETWORK is selected as natwork adapter for the guest

==> NO DNS values get forwarded to the guest

[vasily Levchenko]

Could you please attach the log file from your vm and pcap file?

[petardo]

Replying to Hachiman:

Could you please attach the log file from your vm and pcap file?

Thanks Hachiman. I have uploaded the files requested.

[petardo]

log file

[petardo]

pcap file

[cmtsij]

I also get the same issue. My host is Linux Mint 13 with virtualbox 4.3.2. My guest is Windows XP with SP3.

The guest use NAT function, but alway got no DNS from DHCP. I try to use wireshark in my guest to filter bootp protocol. "DCHP Offer" always missing "Option: (6) Domain Name Server".

I checked my vbox setting:

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/>

[vasily Levchenko]

Replying to cmtsij:

I also get the same issue. My host is Linux Mint 13 with virtualbox 4.3.2. My guest is Windows XP with SP3.

The guest use NAT function, but alway got no DNS from DHCP. I try to use wireshark in my guest to filter bootp protocol. "DCHP Offer" always missing "Option: (6) Domain Name Server".

I checked my vbox setting:

<DNS pass-domain="true" use-proxy="false" use-host-resolver="false"/>

This issue doesn't relate to "NAT networking", please create defect and attach there your VBox.log file and /etc/resolv.conf?

[mdlavin]

I saw this same problem in the 4.2.20 builds. When I reverted back to 4.2.18 the problem went away.

[mdlavin]

Also worth noting, I saw this with a Linux host and guest, not Windows.

[Klaus Espenlaub]

4.2.20 has similar NAT improvements as 4.3, which should make sure that DNS changes are picked up in a timely manner by registering for DNS config change notifications. This was most tested on OSX host, where it definitely works, but maybe there is some problem on other platforms (notification too early or some such).

[vasily Levchenko]

cmsij and mdlavin, please open defect against "NAT" not "NAT Network". "NAT Network" had appeared in 4.3.

[dr_barnowl]

This is still a problem as of 4.3.18

Confirmed that you can ping external hosts - as long as you use their IP address.

I guess the workaround is to manually configure DNS servers (which won't allow you to resolve other guests on the NAT network, but you can put them in your host file.)

For my ubuntu server, this was useful ​Static DNS with DHCP

For Windows, you can meddle with the IPv4 settings of your virtual network adapter from the properties panel.

I just set both to Google's DNS ; I'll probably just turn off DHCP and give them static addresses too, so I can rely on them resolving each other via their hostnames put in hosts files.

I'm guessing that "NAT Network" either doesn't implement a DNS service or isn't sending it to the guests when they do a DHCP request ; it would be easier if this worked, of course.