diff --git a/doc/source/deploy_install_guides/release/bare_metal/bootstrapping-from-a-private-docker-registry.rst b/doc/source/deploy_install_guides/release/bare_metal/bootstrapping-from-a-private-docker-registry.rst
index 9bcf94cd1..c8b598967 100644
--- a/doc/source/deploy_install_guides/release/bare_metal/bootstrapping-from-a-private-docker-registry.rst
+++ b/doc/source/deploy_install_guides/release/bare_metal/bootstrapping-from-a-private-docker-registry.rst
@@ -9,6 +9,10 @@ Bootstrapping from a Private Docker Registry
 You can bootstrap controller-0 from a private Docker registry in the event that
 your server is isolated from the public Internet.
 
+.. note::
+    The private docker registry name must not end with ".local" to ensure that
+    the domain name is properly resolved using external DNS.
+
 .. rubric:: |proc|
 
 #.  Update your /home/sysadmin/localhost.yml bootstrap overrides file with the
diff --git a/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst b/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst
index be6203b15..42aa7855c 100644
--- a/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst
+++ b/doc/source/system_configuration/kubernetes/check-new-registry-and-reapply-application.rst
@@ -9,6 +9,10 @@ Check New Registry and Reapply Application
 Perform these steps on both controllers. Use controller-0 first and then swact
 to controller-1 and perform the same steps.
 
+.. note::
+    The private docker registry name must not end with ".local" to ensure that
+    the domain name is properly resolved using external DNS.
+
 .. rubric:: |proc|
 
 #. Run this command to login: