CNAME www.darshrb.in still associated with deleted AWS account CloudFront distribution

I understand your frustration with the CNAME conflict. When you delete an AWS account or CloudFront distribution, the CNAME associations don't immediately disappear from AWS's systems. This is a known issue where CNAMEs can remain associated with deleted resources for a period of time.

Here are some steps to resolve this:

1. Wait for propagation: Even though you've waited over an hour, DNS changes and CNAME disassociations can take up to 24-48 hours to fully propagate through AWS's systems. The cached DNS results and internal associations need time to clear.

2. Verify DNS records: Ensure that all DNS records pointing to the old CloudFront distribution have been completely removed from your GoDaddy DNS settings, including any CNAME records for www.darshrb.in.

3. Contact AWS Support directly: Since this involves account-level associations and potentially requires manual intervention from AWS, you'll need to open a support case with AWS Support. They can verify the status of the CNAME association and manually release it if necessary. You can do this through the AWS Support Center in your new account.

4. Temporary workaround: If you need immediate access, consider using a slightly different subdomain temporarily (like www2.darshrb.in) until the original CNAME is fully released.

The key issue is that AWS maintains CNAME associations to prevent conflicts and ensure proper routing, and these associations persist even after account deletion until they're fully cleared from the system.
Sources
Stop subdomain routing to a different AWS account | AWS re:Post