Investigate DHCP changes that were made

[deniseschannon]

Investigate DHCP changes made to fix #451.

Reference #669's PR for comments from user issues:

Including:

i have set nameservers and override via ros (confirmed values are written in clould-config.yml)
but the values in resolv.conf are still dhcp server values, even after reboot or sudo netconf

I had the same issues and literally just spend all night trying to get it working. Ended up having to put the cloud-config.yml as a write-file. Inception basically. Example: https://gist.github.com/qrpike/cfd5245d4459a2d6efd8
Pretty hacky and I don't like it at all, but it's the cleanest thing I could come up with. I've tried about everything lol

do you know if it's possible to include dynamic some dynamic param into var/lib/rancher/conf/cloud-config.yml?
something like: $(wget -O- http://169.254.169.254/current/meta-data/local-ipv4 into eth1 address?

Having the same problems. I don't know how this could even work with DHCP. The DHCP client (dhcpcd) is running in the background all the time, overwriting any values set manually in resolv.conf.

As far as I can see, the client's configuration (dhcpcd.config) has to be adjusted for this to work as well. Using nooption domain_name_servers, domain_name, domain_search or similar.Having the same problems. I don't know how this could even work with DHCP. The DHCP client (dhcpcd) is running in the background all the time, overwriting any values set manually in resolv.conf.

As far as I can see, the client's configuration (dhcpcd.config) has to be adjusted for this to work as well. Using nooption domain_name_servers, domain_name, domain_search or similar.

[deniseschannon]

Probably also related to the hostname issues: #829

[deniseschannon]

Verified in v0.4.5-rc1

Started with a cloud-config that set the search as google.com.
sudo ros config set rancher.network.dns.search [yahoo.com]
Rebooted machine

New /etc/resolv.conf contains new search.