deploy: ba9c20b

theforeman · Jan 14, 2025 · ef0919c · ef0919c
1 parent 8411a77
commit ef0919c
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 57 deletions.
diff --git a/3.13/Provisioning_Hosts/index-katello.html b/3.13/Provisioning_Hosts/index-katello.html
@@ -2755,25 +2755,8 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
 <p>When the PXE loader is set to <code>none</code>, Foreman does not populate the <code>next-server</code> option into the DHCP record.</p>
 </div>
 <div class="paragraph">
-<p>If the <code>next-server</code> option remains undefined, Foreman uses reverse DNS search to find a TFTP server address to assign, but you might encounter the following problems:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>DNS timeouts during provisioning</p>
-</li>
-<li>
-<p>Querying of incorrect DNS server.
-For example, authoritative rather than caching</p>
-</li>
-<li>
-<p>Errors about incorrect IP address for the TFTP server.
-For example, <code>PTR record was invalid</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>If you encounter these problems, check the DNS setup on both Foreman and Smart&#160;Proxy, specifically the PTR record resolution.</p>
+<p>If the <code>next-server</code> option remains undefined, Foreman calls the Smart&#160;Proxy API to retrieve the server name as specified by the <code>--foreman-proxy-tftp-servername</code> argument in a <code>foreman-installer</code> run.
+If the Smart&#160;Proxy API call does not return a server name, Foreman uses the hostname of the Smart&#160;Proxy.</p>
 </div>
 <div class="paragraph">
 <div class="title">The filename option</div>

diff --git a/3.13/Provisioning_Hosts/index-orcharhino.html b/3.13/Provisioning_Hosts/index-orcharhino.html
@@ -2858,25 +2858,8 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
 <p>When the PXE loader is set to <code>none</code>, orcharhino does not populate the <code>next-server</code> option into the DHCP record.</p>
 </div>
 <div class="paragraph">
-<p>If the <code>next-server</code> option remains undefined, orcharhino uses reverse DNS search to find a TFTP server address to assign, but you might encounter the following problems:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>DNS timeouts during provisioning</p>
-</li>
-<li>
-<p>Querying of incorrect DNS server.
-For example, authoritative rather than caching</p>
-</li>
-<li>
-<p>Errors about incorrect IP address for the TFTP server.
-For example, <code>PTR record was invalid</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>If you encounter these problems, check the DNS setup on both orcharhino and orcharhino&#160;Proxy, specifically the PTR record resolution.</p>
+<p>If the <code>next-server</code> option remains undefined, orcharhino calls the orcharhino&#160;Proxy API to retrieve the server name as specified by the <code>--foreman-proxy-tftp-servername</code> argument in a <code>foreman-installer</code> run.
+If the orcharhino&#160;Proxy API call does not return a server name, orcharhino uses the hostname of the orcharhino&#160;Proxy.</p>
 </div>
 <div class="paragraph">
 <div class="title">The filename option</div>

diff --git a/3.13/Provisioning_Hosts/index-satellite.html b/3.13/Provisioning_Hosts/index-satellite.html
@@ -2382,25 +2382,8 @@ <h3 id="DHCP_Options_provisioning"><a class="anchor" href="#DHCP_Options_provisi
 <p>When the PXE loader is set to <code>none</code>, Satellite does not populate the <code>next-server</code> option into the DHCP record.</p>
 </div>
 <div class="paragraph">
-<p>If the <code>next-server</code> option remains undefined, Satellite uses reverse DNS search to find a TFTP server address to assign, but you might encounter the following problems:</p>
-</div>
-<div class="ulist">
-<ul>
-<li>
-<p>DNS timeouts during provisioning</p>
-</li>
-<li>
-<p>Querying of incorrect DNS server.
-For example, authoritative rather than caching</p>
-</li>
-<li>
-<p>Errors about incorrect IP address for the TFTP server.
-For example, <code>PTR record was invalid</code></p>
-</li>
-</ul>
-</div>
-<div class="paragraph">
-<p>If you encounter these problems, check the DNS setup on both Satellite and Capsule, specifically the PTR record resolution.</p>
+<p>If the <code>next-server</code> option remains undefined, Satellite calls the Capsule API to retrieve the server name as specified by the <code>--foreman-proxy-tftp-servername</code> argument in a <code>satellite-installer</code> run.
+If the Capsule API call does not return a server name, Satellite uses the hostname of the Capsule.</p>
 </div>
 <div class="paragraph">
 <div class="title">The filename option</div>