VBox 4.3 and NAT DNS setting for new NAT Network

[Charles LaCour]

Are the --natdnsproxy# and/or --natdnshostresolver# supposd to work on the new NAT Network?

[noteirak]

It doesn't for you?

[Charles LaCour]

No they don't seem to work. I wanted to get clarification on if they were supposed to work before digging into it further.

I have a number of VMs on my laptop that I use at the office, home and with VPN. To get DNS to work regardless of where I am using the VMs without having to fix the guest resolver I have needed to use these options. In the simple tests I have done it works with NAT but not NAT Network. The host system is running Win 7 and the guest are mostly Linux but some Windows depending on what I need to test.

[noteirak]

Since NAT Network is a brand new feature, I would venture that it is not (yet?) implemented. Only the devs could answer this. Let's hope they do here.

[Charles LaCour]

That would be my guess and that is part of why I posted this. For the majority of testing I do this is the one feature that would be nice to have working. I will have to test the subsequent releases to see if this gets fixed.

For now I will just go back to using Guest VM running pfSense with one NAT interface and one Internal interface.

[djf_jeff]

I can confirm that it doesn't work for the moment. If you run the command (VBoxManage modifyvm "VM name" --natdnsproxy1 on) and the the .vbox file after that, you can see that it only change the NAT section, not the NAT Network section.

This feature would be awesome for me because this means I can have my demo :

- Be independent of the network I am on (gateway, DNS, etc)
- Be able to talk to each other
- Be able to access the internet