7 min read Easy 11.0k

Point a domain name to a VeryCloud VPS

Published on May 16, 2026 at 07:26 PM

Configure DNS records (A, AAAA, CNAME, MX, TXT) at your registrar to point your domain to a VeryCloud VPS. This guide covers web, mail, subdomain and game server SRV cases, without using Plesk.

Introduction

Pointing a domain to a server is the foundation of any hosting. Yet you quickly hit obscure terms: A vs CNAME records, propagation, TTL, glue records, etc.

This guide explains from scratch how to configure DNS to point your-domain.com to a VPS, without going through Plesk (which manages DNS differently and has its own guide).

Prerequisites

A domain name purchased from a registrar (OVH, Gandi, Cloudflare, Namecheap, GoDaddy, etc.)
A VeryCloud VPS with its public IP (visible in the customer area)
Access to your registrar's DNS interface

Step 1: Get your VPS IP

On https://manager.verycloud.fr, open your VPS service:

Public IP (IPv4): e.g. 82.26.157.10
IPv6 (if available): e.g. 2001:41d0:xxxx::1

Note these values.

Step 2: Understand DNS record types

Type	Role	Example
A	Associates a name with an IPv4	`your-domain.com → 82.26.157.10`
AAAA	Associates a name with an IPv6	`your-domain.com → 2001:41d0:...`
CNAME	Alias of another name	`www.your-domain.com → your-domain.com`
MX	Mail server	`your-domain.com → mail.your-domain.com (priority 10)`
TXT	Free text (SPF, DKIM, verifications)	`v=spf1 mx -all`
SRV	Service on specific port	`_minecraft._tcp` → host:port

Step 3: Configure basic records

Main domain (apex / "@")

Type    Name   Value               TTL
A       @      82.26.157.10        3600
AAAA    @      2001:41d0:xxxx::1   3600

The @ (or left blank depending on registrar) represents the domain itself: your-domain.com.

www

Type    Name   Value               TTL
A       www    82.26.157.10        3600

Or as a CNAME:

Type    Name   Value               TTL
CNAME   www    your-domain.com.    3600

⚠️ On the apex (@), you cannot use CNAME (RFC limitation). Always an A.

Subdomains (one per service)

Type    Name        Value               TTL
A       blog        82.26.157.10        3600
A       api         82.26.157.10        3600
A       games       82.26.157.10        3600
A       *           82.26.157.10        3600   # Wildcard (any undefined subdomain)

The wildcard * is useful for apps that create subdomains dynamically (Coolify, Cloudron).

Step 4: Registrar-specific cases

OVH

Customer Area → Web Cloud → Domains → your-domain.com → DNS Zone

Click Add an entry:

Type: A
Subdomain: leave empty for apex, or www
Target: 82.26.157.10
TTL: Default

Cloudflare

Dashboard → your-domain.com → DNS → Records → Add record:

Type: A
Name: @ or www
IPv4 address: 82.26.157.10
Proxy status: DNS only (orange disabled) if you want direct traffic, or Proxied (orange) to go through Cloudflare
TTL: Auto

Gandi

Domains → your-domain.com → DNS Records → Add

BIND text format:

@ 3600 IN A 82.26.157.10
www 3600 IN A 82.26.157.10
* 3600 IN A 82.26.157.10

Namecheap, GoDaddy, Hostinger

All offer a similar graphical interface with Type → Host → Value → TTL. The logic is identical everywhere.

Step 5: Verify DNS propagation

After adding records, propagation takes from a few minutes to 48h depending on TTL and registrars (in practice, 1-2h max).

Command line

On Linux/macOS:

dig +short A your-domain.com
dig +short AAAA your-domain.com
dig +short A www.your-domain.com

Should return the VPS IP.

To test from a specific DNS (Google for example):

dig @8.8.8.8 +short A your-domain.com

On Windows:

nslookup your-domain.com

Online (worldwide check)

Use https://dnschecker.org to see propagation worldwide in real-time.

Step 6: Mail configuration (if mail server on VPS)

See the Mailcow guide for the complete mail server. For DNS, add:

Type    Name             Value                                               Priority
MX      @                mail.your-domain.com.                               10
A       mail             82.26.157.10
A       autodiscover     82.26.157.10
A       autoconfig       82.26.157.10
TXT     @                "v=spf1 mx -all"
TXT     _dmarc           "v=DMARC1; p=reject; rua=mailto:[email protected]"
TXT     dkim._domainkey  "v=DKIM1; k=rsa; p=MIGfMA0GC..."  (generated by Mailcow)

Step 7: Game server configuration

Minecraft (with custom port other than 25565)

Type    Name                              Value
A       play                              82.26.157.10
SRV     _minecraft._tcp.play              0 5 25577 play.your-domain.com

SRV format: priority weight port target.

Players will connect with just play.your-domain.com without typing the port.

FiveM

Type    Name        Value
A       fivem       82.26.157.10

No SRV for FiveM, but you can use a domain name in sv_listingHostOverride of server.cfg.

Step 8: Cloudflare DNS (free and powerful)

If your registrar has a slow or limited DNS interface, transfer DNS management to Cloudflare (free) without changing registrar:

Create a Cloudflare account (free)
Add a site → enter your-domain.com
Cloudflare scans your current DNS
Cloudflare gives you 2 DNS servers (e.g. lina.ns.cloudflare.com)
At your registrar, in DNS servers or Nameservers, replace with Cloudflare's
Wait 1-24h for propagation

Benefits:

Fast and powerful DNS interface
Performant DNS cache
Basic DDoS protection
API for automation

Step 9: Advanced case — Glue records (if you host your own NS)

If you want to host DNS servers on your VPS (rare, generally not recommended), you need to create glue records at the registrar:

ns1.your-domain.com → VPS IP
ns2.your-domain.com → VPS IP (or another VPS)

Then configure an authoritative DNS server (Bind9, PowerDNS) on your VPS.

To avoid unless specifically needed: a single VPS = single point of failure for your DNS.

Step 10: TTL and propagation

The TTL (Time To Live) indicates how long DNS resolvers should cache the response.

TTL	Use
60-300 sec	Migration in progress, imminent change
3600 (1h)	Normal production
86400 (24h)	Stable config, avoids requests

Before a migration, lower TTL to 300 seconds 24h in advance. After migration and OK test, raise it back to 3600+.

Troubleshooting

Domain doesn't point to VPS

Verify the record in registrar interface
Wait 1-2h (initial propagation)
Verify with dig or nslookup
Flush your local DNS cache:

# Linux
sudo systemd-resolve --flush-caches
# macOS
sudo dscacheutil -flushcache
# Windows
ipconfig /flushdns

"Common Name does not match" SSL error

SSL certificate was issued for another domain. Regenerate it after DNS properly points:

sudo certbot --nginx -d your-domain.com

Mail goes to spam

SPF/DKIM/DMARC records are not configured or incorrect. Check each with:

dig +short TXT your-domain.com
dig +short TXT _dmarc.your-domain.com
dig +short TXT dkim._domainkey.your-domain.com

"redirect too many" loop

The www redirects to apex which redirects to www etc. Check your web server config (Nginx/Apache) has only one redirect rule.

Useful commands

# View all records of a domain
dig +noall +answer ANY your-domain.com

# Test specific type
dig +short A your-domain.com
dig +short MX your-domain.com
dig +short TXT your-domain.com

# Test from public resolver
dig @1.1.1.1 +short A your-domain.com
dig @8.8.8.8 +short A your-domain.com

# Full DNS trace (from root servers)
dig +trace your-domain.com

# Reverse DNS (PTR)
dig +short -x 82.26.157.10

Conclusion

You now know how to point a domain to any VeryCloud VPS. DNS management is the foundation of your entire web setup: take time to properly understand A, MX and TXT records.

For pre-installed Plesk sites, the DNS management guide is different and simpler (Plesk automatically manages the DNS zone). See https://verycloud.fr/docs.

Resources

Cloudflare DNS documentation: https://developers.cloudflare.com/dns/
Propagation check: https://dnschecker.org
Full SSL/DNS test: https://mxtoolbox.com
VeryCloud guide — Configure Plesk: available on https://verycloud.fr/docs