EN

Web hosting

Connect a domain registered elsewhere and manage its DNS

Add a domain registered with another registrar to Plesk, point it to your hosting and manage its DNS records without interrupting your email.

6 min read, updated on 18 November 2026

On this page

Your values

Enter them once and the commands in this guide update.

Your domain can stay with its current registrar while displaying a site hosted on Plesk. To do this, you declare the domain in Plesk, then indicate in the DNS where the site is located.

If your domain is managed at HostMyServers, you can also see Point to an IP.

Choose where to manage the DNS

Method A: DNS at the registrar Method B: DNS on Plesk
What you change A few records The domain's name servers
Where you then manage the records At the registrar In Plesk
Existing email Kept if you do not touch the MX records To be recreated in Plesk before the change
Recommended for Most sites Managing everything from Plesk, if support confirms the servers to use

Method A is the simplest and the least risky.

Prerequisites

  • Access to Plesk, see Connect to Plesk interface.
  • Access to your registrar's DNS management.
  • A copy of all current DNS records, especially MX and TXT.

Step 1: add the domain in Plesk

  1. Go to Websites & Domains.
  2. Click Add Domain.
  3. Follow the on-screen instructions and enter your-domain.com. If Plesk asks, indicate that the domain is already registered.
  4. Confirm with OK.

The domain then appears in the list. If your plan no longer allows you to add a site, the subscription's main domain can sometimes be renamed in its hosting settings. This option depends on the hosting provider's policy.

Step 2: find the hosting IP address

  1. Open Websites & Domains > your domain > DNS Settings.
  2. Locate the A record of your-domain.com.
  3. Write down its address. It is called YOUR_SERVER_IP in the rest of this guide.

To check the site before changing the DNS, click Preview under the domain name.

Step 3, method A: keep the DNS at the registrar

A few hours before the change, lower the time to live (TTL) of the records to be modified if you can. The switch will be faster.

In the registrar's DNS zone, create or modify these records:

Type Name Value
A @ or empty, depending on the registrar YOUR_SERVER_IP
CNAME www your-domain.com.

Delete the old A and AAAA records of the domain and of www that target another server. Do not change the MX and TXT records if your email stays with another provider.

If your mailboxes are to be hosted on Plesk, copy the values from the Plesk zone to the registrar: MX, mail, webmail and the SPF TXT record.

Once everything has been checked, you can click Disable in DNS Settings to turn off the Plesk DNS service for this domain, as Plesk recommends when external servers are authoritative. Write down the zone values first, because only the name servers will remain displayed.

Step 3, method B: hand the DNS over to Plesk

  1. Open DNS Settings and compare the zone with your copy.
  2. Add the missing records.
  3. Locate the NS records of the zone. Many registrars require at least two name servers, whereas Plesk only provides one by default. Ask support which servers to use for your hosting.
  4. If DNSSEC is active at the registrar, turn it off before the change.
  5. Replace the name servers at the registrar.

Manage records in Plesk

These actions apply to domains whose zone is served by Plesk. They are done in Websites & Domains > your domain > DNS Settings.

  • Add: click Add Record, fill in the type, name and value, then confirm.
  • Modify: click the record's name.
  • Remove: select the record, then click Remove.

If Plesk then displays an Update button, click it to apply the changes.

Check the result

DNS can take up to 24 to 48 hours to propagate. Query a public resolver to follow the progress:

Terminal
dig @1.1.1.1 +short A your-domain.com
dig @1.1.1.1 +short www.your-domain.com
dig @1.1.1.1 +short MX your-domain.com
dig @1.1.1.1 +short NS your-domain.com

On Windows, use:

PowerShell
nslookup your-domain.com 1.1.1.1

The domain and www must lead to YOUR_SERVER_IP. Then check the site's response:

Terminal
curl -I http://your-domain.com/

Also send a test email to an address on the domain. You can then enable HTTPS and choose the address with or without www.

Troubleshooting

Symptom Likely cause Solution
The old site still appears Propagation in progress or local cache Compare with dig @1.1.1.1, wait for the TTL to expire, then flush your computer's DNS cache
A default page or an error appears The domain has not been added to Plesk, or the IP address is incorrect Go through steps 1 and 2 again
The registrar refuses the CNAME on @ A CNAME cannot coexist with the other records at the root Use an A record for the root and keep the CNAME on www
NXDOMAIN or SERVFAIL after changing name servers Mistyped server, missing zone or DNSSEC still active Check the NS records, the zone in Plesk and the DNSSEC status at the registrar
Email no longer arrives Missing or modified MX records Restore the values from your copy
The registrar refuses the name servers It requires at least two, or they are not valid Ask support which servers to use, or stay with method A
Whois Information replaces DNS Settings Plesk does not manage the DNS of this domain Manage your records at the registrar
The Let's Encrypt certificate fails An A or AAAA record targets another server Fix the DNS, see Enable a Let's Encrypt certificate