🌐 Manage DNS zone from Plesk#

This guide explains how to modify your web hosting's DNS zone through the Plesk interface, with a focus on different record types and SRV configuration for Minecraft.

1️⃣ Access DNS management#

1. Log in to Plesk or via the customer area.
2. Select your domain from the list.
3. Click on DNS Zone in the menu.

2️⃣ Types of DNS records#

Here is a table of the main DNS record types you can configure:

3️⃣ Add or modify a record#

Create a new record#

1. Click on Add Record.
2. Select the desired record type.
3. Fill in the required fields:
   • Name: The subdomain or @ for the main domain
   • Value: The IP address, domain name or text depending on type
   • TTL: Cache duration (leave default if uncertain)
4. Click OK to save.

Modify an existing record#

1. Find the record in the list.
2. Click on its name then on Edit.
3. Modify the necessary values.
4. Click OK to save.

4️⃣ SRV configuration for Minecraft#

SRV records allow players to connect to your Minecraft server with just the domain name, without specifying the port.

SRV record format#

For a Minecraft server, the format is:

_minecraft._tcp.your-domain.com

Step-by-step configuration#

1. Add an SRV record:

   • Type: SRV
   • Name: _minecraft._tcp (or _minecraft._tcp.play for a subdomain)
   • Value: Consists of 4 parts separated by spaces

2. SRV value structure:

   priority weight port target-server
   

   Concrete example:

   0 0 25565 srv.your-domain.com
   

3. Parameter explanation:

   • Priority: 0 (lower = higher priority)
   • Weight: 0 (for load balancing, generally 0)
   • Port: 25565 (your Minecraft server port)
   • Target server: srv.your-domain.com (subdomain pointing to your server)

Complete example#

For a Minecraft server on play.example.com:25575:

1. A record for the server:

   • Type: A
   • Name: srv
   • Value: 192.168.1.100 (your server IP)

2. SRV record for simplified connection:

   • Type: SRV
   • Name: _minecraft._tcp.play
   • Value: 0 0 25575 srv.example.com

Result: Players can connect with play.example.com instead of play.example.com:25575.

5️⃣ Tips and best practices#

⏰ DNS propagation#

• DNS changes can take 1 to 24 hours to propagate worldwide.
• Use a shorter TTL (300-600 seconds) for testing or frequent changes.
• Recommended standard TTL: 3600 seconds (1 hour).

🔒 Security#

• Never delete default records without being sure of their purpose.
• Keep a backup of your DNS configuration before major changes.
• MX and NS records are critical for domain operation.

🔧 Verification#

• Use tools like nslookup or dig to verify your changes:

  nslookup your-domain.com
  dig SRV _minecraft._tcp.your-domain.com
  

📝 Common records not to touch#

• NS records from LibraHost (ns1.librahost.fr, ns2.librahost.fr)
• SOA record (Start of Authority)
• MX records if you're using domain email

6️⃣ Troubleshooting#

Common problems#

• Record not found: Check syntax and wait for DNS propagation
• Minecraft SRV not working: Verify that the target server exists (A/AAAA record)
• Email no longer working: Check MX and TXT (SPF) records

Diagnostic tools#

• DNS Checker: Check worldwide propagation
• MXToolbox: Complete DNS tests
• Minecraft SRV Checker: Test Minecraft SRV records specifically

In case of persistent problems, contact LibraHost support with your configuration details.