From 8edf5905059403a845def1372a2c012f1d371d94 Mon Sep 17 00:00:00 2001 From: Zuzana Lena Ansorgova Date: Sat, 21 Dec 2024 00:22:29 +0100 Subject: [PATCH] Fix next-server behavior --- .../modules/ref_options-in-managed-dhcpv4.adoc | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/guides/common/modules/ref_options-in-managed-dhcpv4.adoc b/guides/common/modules/ref_options-in-managed-dhcpv4.adoc index 1876fa6516..83e59809a7 100644 --- a/guides/common/modules/ref_options-in-managed-dhcpv4.adoc +++ b/guides/common/modules/ref_options-in-managed-dhcpv4.adoc @@ -17,16 +17,8 @@ Each TFTP {SmartProxy} then reports this setting through the API and {Project} c + When the PXE loader is set to `none`, {Project} does not populate the `next-server` option into the DHCP record. + -If the `next-server` option remains undefined, {Project} uses reverse DNS search to find a TFTP server address to assign, but you might encounter the following problems: - -* DNS timeouts during provisioning -* Querying of incorrect DNS server. -For example, authoritative rather than caching -* Errors about incorrect IP address for the TFTP server. -For example, `PTR record was invalid` - -+ -If you encounter these problems, check the DNS setup on both {Project} and {SmartProxy}, specifically the PTR record resolution. +If the `next-server` option remains undefined, {Project} calls the {SmartProxy} API to retrieve the server name as specified by the `--foreman-proxy-tftp-servername` argument in a `{foreman-installer}` run. +If the {SmartProxy} API call does not return a server name, {Project} uses the hostname of the {SmartProxy}. `filename`:: The `filename` option contains the full path to the file that downloads and executes during provisioning.