Adding an addon domain in cPanel can fail with (XID xxxxx) A DNS entry for "example.com" already exists. You must remove this DNS entry from this server or all servers in the DNS cluster to proceed. The server already holds DNS for that name, so cPanel won't create a second zone. This guide covers how to troubleshoot it on Domain India shared hosting: what to check in your own account, and when support has to step in.
The error means a DNS zone for the domain already exists on the server. Check your cPanel Domains list and your other hosting accounts; if the domain is there, remove it properly and add it again. If it is nowhere in your accounts, open a support ticket with the full message and XID. The "remove this DNS entry from this server or all servers in the DNS cluster" part is for the server administrator; you can't do it from shared hosting.
This is a troubleshooting summary. For the complete guide, see Fixing the "A DNS entry for the domain already exists" error.
1. Where the conflict comes from
| Cause | Can you fix it? | What to do |
|---|---|---|
| Domain already in your account as an alias, subdomain or addon | Yes | Use it as it is, or remove it in Domains and add it again |
| Domain just removed | Yes | Wait a few minutes and retry |
| Domain in another hosting account you own | Yes | Remove it in that account's cPanel first |
| Leftover zone on the server | No | Open a ticket; support removes it |
| Domain in someone else's account | No | Open a ticket; support may ask you to show you control the domain |
A domain that was once added with Share document root ticked, then removed, is a common source of this. See DNS errors when recreating a shared-document-root addon domain.
2. Checks in your own account
- Search your Domains list.In cPanel, open Domains › Domains and search for the name, including as a subdomain such as
shop.example.com. - Check the Zone Editor.Open Domains › Zone Editor. A domain listed there but not in Domains points to a leftover zone that support must remove.
- Check your other hosting accounts.Open your hosting services and repeat step 1 in each account's cPanel.
- Remove domains the proper way.Always remove a domain in Domains › Domains. Deleting its folder in File Manager leaves the domain and its DNS zone on the server.
3. What the "DNS cluster" line means
The second half of the message is written for server administrators. A DNS cluster is a group of servers that share DNS zones, and removing a zone there needs root access to the server. Older versions of this article gave root commands for it (editing /var/cpanel/users, rebuilding caches). On shared hosting you can't run them, and you don't need to: support does it.
If you administer your own cPanel and WHM server, don't sed lines out of cPanel's internal files. Find the owning account first and use WHM's Delete a DNS Zone or the WHM API. The full guide has the safe steps. Domain India VPS plans don't offer cPanel.
4. Getting support to remove it
Open a ticket at /client/support/new (or /support/ticket if you aren't logged in), or use 24/7 live chat. Include the domain, the full error message with the XID, the cPanel username you are adding it to, and whether the domain was hosted with us before.
After the domain is added, point it to your hosting: see how to change your nameservers and how to add an addon domain.
What causes the "A DNS entry for the domain already exists" error when adding an addon domain?
The server already has a DNS zone for that name. It may be in your own account as an alias, subdomain or addon, in another hosting account, or left over from an earlier removal.
How do I remove the DNS entry "from all servers in the DNS cluster"?
On shared hosting you don't; that needs root access to the server. Open a support ticket with the full error message and XID, and support will remove a stale zone.
I deleted the domain's folder. Why does the error still appear?
Deleting the folder removes only the files. The domain and its DNS zone stay until the domain is removed from Domains in cPanel.
Does support delete a zone that belongs to another account?
Not simply on request. If the zone is attached to another active account, support may ask you to show that you control the domain before changing anything.
Ready to fix it? Check your hosting services for the domain first, then open a support ticket with the XID if it isn't in any of your accounts.
Send us the domain and the full error message, including the XID, and support will find where the old zone comes from.
Open a ticket