I've been trying to prevent dhclient from getting nameserver settings on
eth0 interface.
I could supersede DNS settings with a static nameserver.
I could change settings for eth1 by adding interface "eth1" { ... } section
to dhclient.conf
I found however problems with setting the eth0 interface:
1. The first problem is that removing domain-name and domain-name-servers
has
no effect, it still gets the values from DHCP.
2. The second problem is that adding a interface "eth1" { ... } section
to the dhclient.conf causes Vagrant machine to freeze on reboot at this
moment:
==> client: Configuring and enabling network interfaces...
What can I do to stop dhclient from supplying Vagrant's DHCP settings to
resolvconf, while retaining this for other interfaces than eth0?
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/82cc2aa1-53c2-4f20-8a34-bc861ad3d090%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
