I am experiencing a persistent error: "Failed to create custom domain, please try again" when attempting to add my custom domain to a new Railway project. This happened after I deleted a previous project where the same domain was already verified and "Active".

Technical Details:

• Domain:arkaraweb.com
• Registrar: DomaiNesia
• DNS Provider: Cloudflare (Nameservers have been pointed correctly).
• Target Service Port: 3000 (Defined in Environment Variables as PORT=3000).
• Railway Project URL: https://railway.com/project/e7b52780-4c4d-4721-8a37-bb4d6540f8b6

The Issue: Previously, I had this domain linked to an older Railway project. In that project, the TXT verification was successful (Green/Active), but I had issues with the CNAME record due to my registrar's limitations.

To resolve this, I decided to:

1. Delete the old project entirely.
2. Move my DNS management to Cloudflare.
3. Deploy a new service on Railway.

However, when I try to add the custom domain to the new service, Railway immediately returns: "Failed to create custom domain, please try again" after I select the port (3000).

Troubleshooting Steps Taken:

1. DNS Cleanup: I have removed all old A/CNAME/TXT records from the registrar and Cloudflare.
2. Cloudflare Setup: Added a CNAME record for @ pointing to the new Railway target with Proxy Status: DNS Only (Grey Cloud).
3. SSL Config: Set Cloudflare SSL to Full (Strict).
4. Verification: Checked via dig and DNSChecker; the CNAME record is propagating correctly and pointing to the new Railway address.
5. Browser: Tried using Incognito mode to rule out dashboard caching issues.

Suspected Cause: It seems the domain is still "orphaned" or locked in Railway’s internal database/edge configuration from the previous deleted project, preventing it from being re-associated with a new Service ID.

Request: Could the support team please check if the domain arkaraweb.com is still stuck in the global configuration and clear any existing records manually?