diff --git a/3.11/Provisioning_Hosts/index-katello.html b/3.11/Provisioning_Hosts/index-katello.html index d7f7cec1ad..f4d740d1a6 100644 --- a/3.11/Provisioning_Hosts/index-katello.html +++ b/3.11/Provisioning_Hosts/index-katello.html @@ -2681,25 +2681,8 @@
If the next-server
option remains undefined, Foreman 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 Foreman and Smart Proxy, specifically the PTR record resolution.
+If the next-server
option remains undefined, Foreman calls the Smart Proxy API to retrieve the server name as specified by the --foreman-proxy-tftp-servername
argument in a foreman-installer
run.
+If the Smart Proxy API call does not return a server name, Foreman uses the hostname of the Smart Proxy.
If the next-server
option remains undefined, orcharhino 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 orcharhino and orcharhino Proxy, specifically the PTR record resolution.
+If the next-server
option remains undefined, orcharhino calls the orcharhino Proxy API to retrieve the server name as specified by the --foreman-proxy-tftp-servername
argument in a foreman-installer
run.
+If the orcharhino Proxy API call does not return a server name, orcharhino uses the hostname of the orcharhino Proxy.
If the next-server
option remains undefined, Satellite 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 Satellite and Capsule, specifically the PTR record resolution.
+If the next-server
option remains undefined, Satellite calls the Capsule API to retrieve the server name as specified by the --foreman-proxy-tftp-servername
argument in a satellite-installer
run.
+If the Capsule API call does not return a server name, Satellite uses the hostname of the Capsule.