I am reporting a severe technical failure by x10Hosting that effectively holds my domain hostage.
Domain: tusecreto.x10.mx
Server IP: 198.91.80.155
THE ISSUE:
Their system failed to purge the VirtualHost and DNS configuration after account termination. I have verified this is a server-side "Ghost Record" because the domain remains locked even when I try to register it on a completely different account.
The error "Domain already exists on 198.91.80.155" is hard-coded in their backend.
ESCALATION TAKEN:
- Formal complaint filed with NIC México (Legal Dept) for .MX mismanagement.
- ICANN Case #01557634 opened.
- Upstream provider (INAP/SingleHop) notified of this technical negligence.
I am posting here to warn the community and demand that an x10Hosting System Admin manually clears the orphaned configuration on server 198.91.80.155. Support has been non-responsive for days.
Any advice from the community on how to force a cleanup of orphaned records when the host is silent?
Domain: tusecreto.x10.mx
Server IP: 198.91.80.155
THE ISSUE:
Their system failed to purge the VirtualHost and DNS configuration after account termination. I have verified this is a server-side "Ghost Record" because the domain remains locked even when I try to register it on a completely different account.
The error "Domain already exists on 198.91.80.155" is hard-coded in their backend.
ESCALATION TAKEN:
- Formal complaint filed with NIC México (Legal Dept) for .MX mismanagement.
- ICANN Case #01557634 opened.
- Upstream provider (INAP/SingleHop) notified of this technical negligence.
I am posting here to warn the community and demand that an x10Hosting System Admin manually clears the orphaned configuration on server 198.91.80.155. Support has been non-responsive for days.
Any advice from the community on how to force a cleanup of orphaned records when the host is silent?
Also to add here that GDPR applies to personal data and when we say personal data we mean any information relating to an identifiable natual person ( e.g. name, email, ip, billing data, logs etc ). A DNS Zone entry on a VirtualHost configuration is not automatically personal data but infrastructure metadata. It will becomes relevant to GDPR if the subdomain directly identifies you as a natural person. There are no GDPR articles as far as I know that will force a hosting service provider to instant delete DNS Records.
Now i get the part that you want this to be removed but as Bear mentioned, they have the right per their TOS to not allow multiple accounts and it seems that this is the case. The luck of instant support might be the real "thread" here ( possible ) but the GDPR matters are out of scope per my personal opinion
Now i get the part that you want this to be removed but as Bear mentioned, they have the right per their TOS to not allow multiple accounts and it seems that this is the case. The luck of instant support might be the real "thread" here ( possible ) but the GDPR matters are out of scope per my personal opinion
To Bear,
1. Regarding "Multiple Accounts": You are misinterpreting a technical troubleshooting step as a violation of terms. Attempting to register the domain on a clean environment was a "Diagnostic Test" to confirm if the lock was at the Database level or the Server Configuration level. It confirmed the latter: A stale VirtualHost entry.
2. Regarding GDPR/Registry: I am not here to debate which regulatory body handles what. I have provided the official Legal Ticket #ML100319224 from Registry.MX. They have accepted the case. If they felt it was "none of their business" as you claim, they wouldn't have assigned a legal investigator to it.
3. The "Intentional" theory: If a hosting company intentionally leaves "Ghost Records" to block reuse, they should state that in their TOS. Otherwise, it is a technical bug. Professional automation (like cPanel/DirectAdmin/Custom API) is designed to purge records upon termination. Leaving "zombie" configs is not a security feature; it’s poor housekeeping.
The fact remains: There is a technical deadlock on 198.91.80.155. I am documenting this for the Registry's investigation. Whether you agree with my methods or not, the Legal Ticket is active, and that is what matters.
1. Regarding "Multiple Accounts": You are misinterpreting a technical troubleshooting step as a violation of terms. Attempting to register the domain on a clean environment was a "Diagnostic Test" to confirm if the lock was at the Database level or the Server Configuration level. It confirmed the latter: A stale VirtualHost entry.
2. Regarding GDPR/Registry: I am not here to debate which regulatory body handles what. I have provided the official Legal Ticket #ML100319224 from Registry.MX. They have accepted the case. If they felt it was "none of their business" as you claim, they wouldn't have assigned a legal investigator to it.
3. The "Intentional" theory: If a hosting company intentionally leaves "Ghost Records" to block reuse, they should state that in their TOS. Otherwise, it is a technical bug. Professional automation (like cPanel/DirectAdmin/Custom API) is designed to purge records upon termination. Leaving "zombie" configs is not a security feature; it’s poor housekeeping.
The fact remains: There is a technical deadlock on 198.91.80.155. I am documenting this for the Registry's investigation. Whether you agree with my methods or not, the Legal Ticket is active, and that is what matters.
- Page :
- 1
- 2
There are no replies made for this post yet.