Vagrant 1.2.2 warnings

leap local status              
 = created test/Vagrantfile
There were warnings and/or errors while loading your Vagrantfile.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.

Warnings:
* `config.vm.customize` calls are VirtualBox-specific. If you're
using any other provider, you'll have to use config.vm.provider in a
v2 configuration block.

There were warnings and/or errors while loading your Vagrantfile.
Your Vagrantfile was written for an earlier version of Vagrant,
and while Vagrant does the best it can to remain backwards
compatible, there are some cases where things have changed
significantly enough to warrant a message. These messages are
shown below.

"The vagrant config format changed since v1.1":http://docs.vagrantup.com/v2/vagrantfile/version.html

config.vm.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]

should be in this format for vagrant >=1.1:

http://docs.vagrantup.com/v2/virtualbox/configuration.html

(from redmine: created on 2013-05-04, closed on 2013-07-26, relates #2395 (closed))