Strange issue of not being able to add an addon domain - say DNs exists, bit it doesn't

[Avo19]

I had previously added a domain xxx.com as 'addon' that uses the registrars nameservers. Domain resolved ok, but I had some issues cloning a WP site to it, and was getting 500 errors.

In the end I decided to remove the addon domain and start again. But when I try to re-add I get the error msg "Error: (XID hmx3em) (XID xj9g8y) A DNS entry for the domain “addondomain.acountdomain.com” already exists, at "/usr/local/cpanel/Cpanel/Admin/Modules/Cpanel/subdomain.pm line 176."

The addon doesn't share the document root. Note there's 10 other addons under this account, and none have any issues, only this one.

I've deleted the domain DNS via WHM "Delete a DNS Zone" function, have checked the httpconf for any left over entry, checked userdata & users.cache and can see no entries.

The domain folder has been removed under /home/accountdomain/.

Restarted, DNS, fpm, http server and in desperation rebooted the server.

But still nada. So my question is, where is cPanel seeing this DNS entry, and more importantly, how can I resolve, so I can re-add the domain

 

[ResellerWiz]

I assume you are not using DNS Clustering?

 

[Avo19]

I assume you are not using DNS Clustering?

No, I'm not

 

[ResellerWiz]

Have you tried rebuilding httpd.conf to make sure everything is good?:

/usr/local/cpanel/scripts/rebuildhttpdconf

Also, check to make sure the subdomain doesn’t exist for the accounts main domain and also check the DNS zone for the main domain that the subdomain isn’t there either.

 

[Avo19]

Thanks, have done all of that. Have even greped the domain name in /var, /etc and /home and only find mention in logs or in virtfs files, which are no longer used, as I've removed all shell access for the account. The error msg appears to refer to a DNS entry, and the location it gives is a line number of a script, which is an error msg

 

[ResellerWiz]

Since addon domains create a subdomain in the main account domain, try grep’ing for the subdomain, not the domain name of the addon domain name, in: /var/named/

If you still can’t find anything, your best bet would be to open a ticket so they can have a closer look.

 

[cPRex]

Thanks, @ResellerWiz. I like all those ideas as well, so it might be time for a ticket if the issue hasn't been resolved yet.

 

[Avo19]

Since addon domains create a subdomain in the main account domain, try grep’ing for the subdomain, not the domain name of the addon domain name, in: /var/named/

If you still can’t find anything, your best bet would be to open a ticket so they can have a closer look.

Thanks, but I've done that. In the end, I decided I'd wasted too much time on this, so I installed the domain under another, account, on the same server.
Cheers, and thanks for your help.