diff --git a/docs/source/markdown/podman-machine-info.1.md b/docs/source/markdown/podman-machine-info.1.md
index 2cc85e100f..320afc7733 100644
--- a/docs/source/markdown/podman-machine-info.1.md
+++ b/docs/source/markdown/podman-machine-info.1.md
@@ -11,6 +11,12 @@ podman\-machine\-info - Display machine host info
 Display information pertaining to the machine host.
 Rootless only, as all `podman machine` commands can be only be used with rootless Podman.
 
+*Note*: The `DefaultMachine` field in the `Host` output does not suggest that
+one can set a default podman machine via system connections. This value represents
+the current active system connection associated with a podman machine. Regardless
+of the default system connection, the default podman machine will always be
+`podman-machine-default`.
+
 ## OPTIONS
 
 #### **--format**, **-f**=*format*
diff --git a/pkg/domain/entities/machine.go b/pkg/domain/entities/machine.go
index 74c025db5d..c6db89d3c1 100644
--- a/pkg/domain/entities/machine.go
+++ b/pkg/domain/entities/machine.go
@@ -28,8 +28,14 @@ type MachineInfo struct {
 
 // MachineHostInfo contains info on the machine host
 type MachineHostInfo struct {
-	Arch             string `json:"Arch"`
-	CurrentMachine   string `json:"CurrentMachine"`
+	Arch           string `json:"Arch"`
+	CurrentMachine string `json:"CurrentMachine"`
+	// TODO(6.0): Change `DefaultName` to `ActiveMachineConnection` to fix address
+	// confusion as shown in https://github.com/containers/podman/issues/23353.
+	// The name `DefaultMachine` can cause confusion with the user in thinking that
+	// they can set a default podman machine via system connections. However,
+	// regardless of which system connection is default, the default podman machine
+	// will always be podman-machine-default.
 	DefaultMachine   string `json:"DefaultMachine"`
 	EventsDir        string `json:"EventsDir"`
 	MachineConfigDir string `json:"MachineConfigDir"`