> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers-1/quickstart.md).

# Quick Start

The DNS service allows you to manage your company’s domains and your customers’ domains from the Plenit dashboard, alongside the rest of the services.

> #### 📘 What you'll achieve
>
> This guide walks you through the essential process: creating the zone, delegating the domain from your registrar, publishing the first records, and verifying that everything resolves correctly.

### Before you start

To follow this guide, you need:

* Access the administration panel at admin.plenit.com with DNS permissions.
* Have a registered domain. Plenit hosts and manages the domain’s DNS zone; the domain registration is kept with your usual registrar.
* Be able to access your registrar’s panel to change the domain’s nameservers.

<figure><img src="https://files.readme.io/b0467878a47c2cb91afb5070041b07bf6fb29dc4a892b341c7125d87c6d82e91-01_dashboard.png" alt=""><figcaption></figcaption></figure>

### Step 1. Create the DNS zone

In the dashboard, go to **DNS** and click **New zone**. Enter the domain name (for example, yourdomain.com) and confirm.

The zone is created instantly with its system records (SOA and NS) and is ready to receive your records.

> 📘 **New zone or migration?**
>
> If the domain already has records published with another provider, create them in the Plenit zone **before** delegating, so there is no service interruption.

### 2. Choose the location

Start the wizard. The first step is the **location**: select the region where you want your server to be hosted. You have Madrid (EU-DEV1) and Paris (EU-DEV5), among others.

<figure><img src="https://files.readme.io/f670c617e56094ba061c7e06e89c0dfc9129786179a01b4083da3b31fdbd34ef-04_location.png" alt=""><figcaption></figcaption></figure>

> 📘 Madrid or Paris?
>
> Choose the region closest to your users or to the rest of your infrastructure to reduce latency.

### 3. Define CPU and RAM

Now you choose the **compute resources**: how many CPUs and how much RAM the server will have. Adjust it to the workload you plan to put on it; you can always resize it later.

<figure><img src="https://files.readme.io/b76e10995237955e9b3b8f0f7aa1bd808943472dac315762ea8d51ca8b82bd1f-05_size.png" alt=""><figcaption></figcaption></figure>

### 4. Select the image

Choose the **operating system** for the server. You can start from a ready-made image (for example, Windows) or switch between the tabs **My images** and **Marketplace** to use your own or one from the catalog.

<figure><img src="https://files.readme.io/eb7baa3dc4c843a251b954fc8d9d29d607536e323b7c9c354d4e58b2b4605bcb-06_image.png" alt=""><figcaption></figcaption></figure>

### 5. Add applications (optional)

If you want, you can preinstall **applications** on the image, such as Google Chrome. It's optional: if you don't need any, continue.

<figure><img src="https://files.readme.io/4f500e53b8f1b2ee533bd6a526a17862586afb4b8970d2c93cb80a53367b2a69-07_applications.png" alt=""><figcaption></figcaption></figure>

### 6. Configure the disk

Define the **storage**: the disk size and, if needed, the associated backup.

<figure><img src="https://files.readme.io/31b72404b56fad58a64da031dd9f45733b923de1a2e878dc3506414b07b9589b-08_disks.png" alt=""><figcaption></figcaption></figure>

> 👍 Recommendation
>
> Enabling backup from the start saves you headaches: it's your safety net for recovering data if something goes wrong.

### 7. Choose the network

Select the **network type**. For most deployments, a **VPC** network gives you an isolated and controlled environment.

<figure><img src="https://files.readme.io/e3d047553f66cd468f284f3ee9b1d676b4a0c8e76384b8101f9ddd57c9564e20-09_network.png" alt=""><figcaption></figcaption></figure>

### 8. Final settings: name and access

Final step of the wizard: give the **name** to the server and enable access via **RDP** if you're going to connect remotely.

<figure><img src="https://files.readme.io/131bf266d04b4508dd6bcb8c646eb71fd3cb7ed89eff52c926ff89b99ff6b340-10_settings.png" alt=""><figcaption></figcaption></figure>

### ~~9~~. Create the server

Confirm and create the server. We'll deploy it and show you a notice with the **temporary password** for access.

<figure><img src="https://files.readme.io/862a459485a101173ae594c512325ac7298cdd9f3343f3f2e3fa7ad94d8e46a1-11_password_modal.png" alt=""><figcaption></figcaption></figure>

> #### ❗️ Save the password
>
> It's temporary and is only shown once.&#x20;
>
> Copy it before closing the notice and change it on your first login.<br>

### Check that everything is ready

Go back to **Servers**: your new server should already appear in the list with its status. When it's active, you can connect with the user and temporary password you just saved.

> #### 👍 Done
>
> You now have your first server deployed on Plenit.&#x20;
>
> From here you can connect, install whatever you need, and start working.<br>

Was this guide helpful? If you've gotten stuck at any step or something doesn't match what you see on screen, let us know from [**Tickets**](/docs-en/support/tickets.md) and we'll review it.


---

# 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://docs.plenit.com/docs-en/productos/servers-1/quickstart.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.