summaryrefslogtreecommitdiff
path: root/doc/rtd/conf.py
diff options
context:
space:
mode:
authorJoshua Harlow <harlowja@yahoo-inc.com>2013-01-25 17:11:33 -0800
committerJoshua Harlow <harlowja@yahoo-inc.com>2013-01-25 17:11:33 -0800
commitd9fe11ca2bef6860847c8fba5dad7a7a34ed3faf (patch)
treeba77e18272046140e67b02db70f95d4ecac9f40d /doc/rtd/conf.py
parent769419522585ff4c93f6d2c71990b137757f6a32 (diff)
parent94c37c074aed4036160881f4f3a28d35f868d006 (diff)
downloadvyos-cloud-init-d9fe11ca2bef6860847c8fba5dad7a7a34ed3faf.tar.gz
vyos-cloud-init-d9fe11ca2bef6860847c8fba5dad7a7a34ed3faf.zip
Adding a resolv.conf configuration module (LP: #1100434)
Managing resolv.conf can be quite handy when running in an environment where you would like to control DNS resolution, despite being provided DNS server information by DHCP. This module will allow one to define the structure of their resolv.conf and write it PER_ONCE. Right now this makes the most sense on RedHat, and therefore, has defined 'distros' as such. Note that when a config drive is used, and dhcp is not used that this module may not be applicable since in the RedHat based distros the config drive typically contains a ubuntu style network configuration which contains nameservers that can be used in /etc/resolv.conf, but for other types of datasources it is useful to have a module which can be specifically configured to write out /etc/resolv.conf
Diffstat (limited to 'doc/rtd/conf.py')
0 files changed, 0 insertions, 0 deletions