Docs Menu
Docs Home
MongoDB Cloud Manager

Host Mappings

On this page

  • Preferred Hostnames
  • Aliases

Host mappings are based on the data that the Monitoring retrieves on a regular interval. Cloud Manager regenerates the entries on the Host Mappings page after each retrieval.

Host mappings are displayed in three-column rows:

The preferred hostname and port for the deployment.
One alternative hostname or address and port for the deployment.
Last Updated
The timestamp when the host mapping was updated.

If a host has multiple aliases, each mapping of host to alias is listed in its own row.

The preferred hostname also appears in the Name column of the Deployment page. This hostname can be a hostname, an FQDN, an IPv4 address, or an IPv6 address. If you want a different preferred hostname than what Cloud Manager chose, regenerate the list of mappings in one of the following ways:

  • Specify constraints on how Cloud Manager picks a preferred hostname. For more information, see Preferred Hostnames in Edit Project Settings.

  • Reset the mapping list. For more information, see Reset Duplicates in Edit Project Settings.


Resetting duplicates and setting constraints on the selection of a preferred hostname cause Cloud Manager to lose the monitoring history for affected hosts. Chart data based on this history is also lost.

Depending on what Cloud Manager obtains from a monitored host, the alias may be in any one of the following forms:

  • Fully qualified domain name (FQDN)

  • Internal hostname

  • External IPv4 or IPv6 address

  • Internal IPv4 or IPv6 address


To prevent naming conflicts, Cloud Manager does not use localhost or similiar local designations for new or remapped hosts unless no other hostname option is possible.


Add a Custom MongoDB Build


Migrate Deployments