> 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/rdm/knowledge-base/knowledge-base-articles/entry-settings/domain-registrar.md).

# Domain registrar

Configure the Domain registrar entry in Remote Desktop Manager to store domain name, registrar, renewal, expiration, name servers, and WHOIS details.

This article details the many settings and options available for ***Domain registrar*** entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong> — Opens the entry in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the entry in a separate window. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Domain name</strong></td><td>The registered domain name. Click the <em><strong>Refresh</strong></em> button in the field to query WHOIS for this domain and fill in the registrar, dates, domain status, name servers, and WHOIS information that the query returns.</td></tr><tr><td><strong>Registrar</strong></td><td>The name of the registrar the domain is registered with.</td></tr><tr><td><strong>Registrar URL</strong></td><td>The website address of the registrar.</td></tr><tr><td><strong>Account number</strong></td><td>The account number with the registrar.</td></tr><tr><td><strong>Annual cost</strong></td><td>The yearly cost of the domain registration.</td></tr><tr><td><strong>Auto-renewal</strong></td><td>Indicates that the domain registration renews automatically.</td></tr><tr><td><strong>Registration date</strong></td><td>The date the domain was registered. Select the checkbox to set the date in the date picker.</td></tr><tr><td><strong>Expiration date</strong></td><td>The date the domain registration expires. Select the checkbox to set the date in the date picker. Leave the checkbox cleared for no expiration.</td></tr><tr><td><strong>Certificate</strong></td><td>Links a certificate entry from the vault to the domain.</td></tr><tr><td><strong>Updated date</strong></td><td>The date the domain registration was last updated. Select the checkbox to set the date in the date picker.</td></tr><tr><td><strong>Domain status</strong></td><td>The status codes of the domain.</td></tr><tr><td><strong>Name servers</strong></td><td>The name servers of the domain.</td></tr><tr><td><strong>WHOIS</strong></td><td>Additional information returned by the WHOIS query.</td></tr></tbody></table>


---

# 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/rdm/knowledge-base/knowledge-base-articles/entry-settings/domain-registrar.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.
