- Newest
- Most votes
- Most comments
If I understand the question correctly: You're changing the private IP address of your EC2 instance to the public IP it has been assigned and that is breaking the network connectivity. If so, yes - that's exactly as expected.
Could you explain why you need to do this. "due to our DNS Infoblox" is not enough information. There is documentation available for running Infoblox on AWS but I'm unsure where to point you because of the lack of detail.
No We are configuring Static Private ip inside the machine, which is already assigned from aws side. Since this machine would be provision as domain controller and having third party DNS infoblox dynamic ip is not working while registering for SRV record.[]()
If you know in advance what it needs to be then the private IP can be set at the time the instance is launched.
AWS Console -> Launch instance -> Network settings -> Advanced network configuration
It can also be included in a Launch Template.
As well as AWS Console, it can obviously also be done using Cloud Formation, Terraform, etc.
Relevant content
- asked 2 years ago
AWS OFFICIALUpdated 6 months ago- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
No We are configuring Static Private ip inside the machine, which is already assigned from aws side. Since this machine would be provision as domain controller and having third party DNS infoblox dynamic ip is not working while registering for SRV record.