> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/concepts/intermediate-concepts/host-linking-and-host-management.md).

# Host linking and host management

Host linking and host management in Devolutions Server centralize machine information in a single host entry reused across multiple sessions.

Host linking and host management in Devolutions Server centralize machine information in a single host entry that is reused by multiple sessions. Instead of repeating the same DNS name, IP address, and description in many RDP, SSH, and web entries, you link them all to one host record.

When a server moves or changes name, you update only the host entry and every linked session automatically follows. This approach reduces duplication, simplifies audits of where a system is used, and prepares the environment for inventory or lifecycle management features in connected tools such as Remote Desktop Manager.

#### Related topics

* [Entries](/server/web-interface/vaults/entries.md)

#### See also

* [Host linking and host management](https://docs.devolutions.net/rdm/concepts/intermediate-concepts/host-linking-and-host-management)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/server/concepts/intermediate-concepts/host-linking-and-host-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.