- Newest
- Most votes
- Most comments
Hi,
This video will be helpful as well: https://www.youtube.com/watch?v=QcCgSWrbkSs
It shows how to check "from the outside" if the reverse DNS issue exists or not and then how to fix it.
Didier
If you're seeing the error message that your Elastic IP address cannot be released because it's locked to your account, there are a few steps you can take to resolve this issue:
-
Check if the Elastic IP has a reverse DNS (rDNS) record associated with it. This is a common reason why Elastic IPs get locked to accounts. You can verify this using the AWS CLI command:
aws ec2 describe-addresses-attribute --allocation-ids [your-eipalloc-id] --attribute domain-name -
If there is an rDNS record, you'll need to have it removed. You can submit a request through the AWS Support contacts form specifically for rDNS limits removal.
-
If you've confirmed there's no rDNS record or you're still unable to release the IP after removing it, you'll need to contact AWS Support. You can do this by:
- Signing into the AWS Management Console
- Navigating to the AWS Support Center
- Creating a case (select "Service limit increase" and "Elastic IP Address Limit")
- Providing the allocation ID and error message in your request
- Even without premium support, you should be able to create a support case under the "Account and billing" category since this is related to a service you're being charged for.
Once AWS Support removes the lock on your Elastic IP address, you'll be able to release it and stop incurring charges for the unused IP.
Sources
Elastic IP addresses could not be released. | AWS re:Post
How do I get an elastic IP address un-locked without premium support? | AWS re:Post
Relevant content
asked 2 years ago
asked 4 years ago
asked 3 years ago
asked 3 years ago
