> For the complete documentation index, see [llms.txt](https://meshnet.nordvpn.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meshnet.nordvpn.com/features/renaming-devices.md).

# Renaming devices in Meshnet

When you enable Meshnet, your device gets a default Nord name. However, Meshnet also has a device renaming feature, enabling you to assign custom nicknames to your peer devices. These nicknames serve as visual identifiers and host names, allowing convenient connections between the devices. 

Nicknames for personal devices are synced across all devices linked to the same Nord account. This synchronization ensures a consistent experience when switching between your Meshnet devices.

Nicknames for external devices are synced across all personal devices that have the same external device added to their Meshnet. These nicknames are only visible to your account. External peer devices do not see the new name you assign to them.

* [Renaming devices on Windows](/features/renaming-devices/windows.md)
* [Renaming devices on Android](/features/renaming-devices/android.md)
* [Renaming devices on iPhone/iPad](/features/renaming-devices/ios.md)
* [Renaming devices on macOS](/features/renaming-devices/macos.md)
* [Renaming devices on Linux](/features/renaming-devices/linux.md)

After applying a nickname, you can access the renamed device with all of these identifiers:

<table><thead><tr><th width="209">Identifier</th><th>Example</th></tr></thead><tbody><tr><td>Nickname</td><td>home-pc</td></tr><tr><td>Nickname + <code>.nord</code></td><td>home-pc.nord</td></tr><tr><td>Nord name</td><td>secret.meerkat-everest.nord</td></tr><tr><td>Meshnet IP address</td><td>100.74.82.230</td></tr></tbody></table>

<details>

<summary>Examples of nickname usage</summary>

* Pinging a renamed device called `work-macbook`:

  <div align="left"><figure><img src="/files/FMScxyorVIGQGXxA3oE3" alt="Terminal output showing a successful ping command."><figcaption></figcaption></figure></div>

  &#x20;
* [Connecting over SSH](/how-to/remote-access/access-remote-systems-over-ssh.md) to a renamed device called `ubuntu-server`:

  <div align="left"><figure><img src="/files/zJsW0Rxm6N6zxqmqchzP" alt="SSH command in terminal."><figcaption></figcaption></figure></div>

  &#x20;
* Accessing a [web server](/how-to/joint-projects/nginx-web-server-access.md) hosted on a renamed peer device called `raspberry-pi`:

  <div align="left"><figure><picture><source srcset="/files/A3a0e6zi9wIu9uqGRoXb" media="(prefers-color-scheme: dark)"><img src="/files/4ouSi8Fnvd6OjB2rT3c5" alt="Internet browser displaying an nginx web server."></picture><figcaption></figcaption></figure></div>

  &#x20;
* Connecting to a renamed device called `home-pc` using a [remote desktop](/how-to/remote-access/log-in-to-pc-remotely.md) app:

  <figure><img src="/files/LVIeE9u8hlC9ySM4crmg" alt="&#x22;Remote Desktop Connection&#x22; app window with the device&#x27;s nickname entered in the &#x22;Computer&#x22; field."><figcaption></figcaption></figure>

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://meshnet.nordvpn.com/features/renaming-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.