Point your domain to your dedicated server
Find your server's public IP, add A and MX records for your CR Servers domain, and cover the mail and firewall checks that matter on a dedicated server or colocation.
A short checklist to make a domain registered with CR Servers open your dedicated server or colocated equipment. The full step-by-step DNS guide is Manage DNS records for your domain.
1. Find the public IP you want to use
For a dedicated server, open the client area, select the server, and copy its public IPv4 address (it is also in your welcome email). A server can have more than one public IP; use the one your web or mail service listens on. For colocation, use the public IP configured on your own equipment.
2. Make sure the domain uses your registrar's DNS
Records you add only take effect when the domain uses the DNS included with your domain registration (dns1.name-services.com through dns5.name-services.com), not the CR Servers hosting nameservers. Follow steps 1 and 2 of Manage DNS records for your domain, including the warnings about shared hosting, email, and existing records.
3. Add the records
In the client area, open Domains, select your domain, and open DNS Management. Add:
| Hostname | Type | Value |
|---|---|---|
@ |
A | Your server's public IPv4 address |
www |
A | Your server's public IPv4 address |
If the same server sends or receives the domain's email, also add an A record for your mail host (for example mail) and the MX record for the domain pointing at it, plus any SPF or DKIM TXT records your mail software needs.
4. Mail servers: set reverse DNS
Receiving mail servers expect the sending IP to have a reverse DNS (PTR) record that matches a hostname you control, and that hostname should point back at the same IP. Add the forward A record first, then request reverse DNS for the IP.
5. Check that your server answers
DNS only sends visitors to the IP. The server still has to accept the connection:
- Your service is running and listening on the expected port (for example
sudo ss -tlnp | grep -E ':80|:443'on Linux). - The server firewall allows those ports (80 and 443 for a website, 25 and 587 for mail if you run a mail server).
curl -I http://YOUR.IP.ADDRESSreturns a response from the server itself.
If you cannot reach the server after a firewall change, see Access your dedicated server with SSH or open a ticket and ask for a console check.
6. Verify
Run dig +short A yourdomain.com and confirm it returns your server's IP. Changes are usually visible within minutes, but some networks take up to a few hours.
On this page