From cb7a84e8106398cd021237f41e7dd1e1e503c286 Mon Sep 17 00:00:00 2001 From: "David Kaspar [Dee'Kej]" Date: Tue, 2 May 2017 23:17:19 +0200 Subject: DHCP_FQDN and DHCP_SEND_HOSTNAME introduced The way DHCP_HOSTNAME is being sent to DHCP server has been completely reworked... DHCP_FQDN now allows user to specify fully qualified domain name to be sent to DHCP server instead of just using simple hostname. This option takes precedence before DHCP_HOSTNAME variable. DHCP_SEND_HOSTNAME can be used to tell initscripts to not send either DHCP_HOSTNAME or DHCP_FQDN to DHCP server. Both of these options should behave same as they do in NetworkManager. --- examples/networking/ifcfg-eth-dhcp | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'examples') diff --git a/examples/networking/ifcfg-eth-dhcp b/examples/networking/ifcfg-eth-dhcp index 2dd687ab..58d46bf8 100644 --- a/examples/networking/ifcfg-eth-dhcp +++ b/examples/networking/ifcfg-eth-dhcp @@ -7,5 +7,8 @@ DEVICE=eth0 BOOTPROTO=dhcp HWADDR=00:11:22:33:44:55 ONBOOT=yes -DHCP_HOSTNAME=host1 +# WARNING: When both DHCP_HOSTNAME and DHCP_FQDN are specified, +# only DHCP_FQDN will be used. +DHCP_HOSTNAME=host1 +DHCP_FQDN=host1.foo.bar.com -- cgit v1.2.1