Bobcares

EC2 Error The address with allocation id cannot be released – How to fix

by | Jul 17, 2021

Wondering how to fix EC2 error The address with allocation id cannot be released? We can help you!

Often our customers report to us that they get this error while releasing an Elastic IP address from their Amazon EC2 instance.

Here at Bobcares, we handle requests from our customers to fix similar issues as a part of our Server Management Services.

Today let’s see how our Support Engineers fix this for our customers with EC2 instances.

How to fix EC2 Error The address with allocation id cannot be released

Before going into the steps for fixing this error we will see what causes this error.

A typical error looks like the one given below:

Error [IP address]: The address with allocation id [allocation id] cannot be released because it is locked to your account
Cause:

Generally, this error message generates when a reverse Domain Name System (rDNS) record is created for the Elastic IP address.

Steps to fix “Error The address with allocation id cannot be released”

We will see the steps that our support engineers follow to fix this error for our customers:

1. Confirm whether rDNS is set for your Elastic IP address

1.  Firstly we have to connect to the instance via SSH.

2.  Run the host command.

$ #host your_IP_address

If the Elastic IP address has an rDNS set we will get an output similar to the following:

$ your_IP_address.in-addr.arpa. domain-name-pointer mail.domain.com

2. Request removal of the rDNS entry

1. Firstly we have to make a Request to remove the email sending limitations form.

2. And we must complete the form using the following information:

Email Address: Your email address.

Use Case Description: Your specific use case for requesting rDNS removal.

Elastic IP address: This field is optional.

Reverse DNS record: This field is optional.

Reverse DNS Record for EIP 1: Enter please remove rDNS.

Reverse DNS Record for EIP 2: Leave blank.

Note: Adding Elastic IP addresses is optional. If needed we can add up to 100 Elastic IP addresses and 100 reverse DNS records.

3. Finally, click Submit.

Note: Removing the rDNS might take a few days to propagate through the system.

3. Release the Elastic IP address

1. Once we receive confirmation about the removal of rDNS, we can run the host command to verify

$ #host your_IP_address

We may get an output similar to the following:

$ your_IP_address.in-addr.arpa. domain-name-pointer ec2-54-244-68-210.us-west-2.compute.amazonaws.com.

2. Now, open the Amazon EC2 console, and click on Elastic IPs.

3. And select the Elastic IP address, click Actions

4. Finally click on Release.

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to fix this error for our customers using EC2 instances.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.