跳至内容

NLB lost one of assigned IP adresses.

0

Hello community.

I have a Network Load Balancer in my infrastructure. It was deployed to the two private subnets in two availability zones. It was working well until I noted that one of the assigned internal IP addresses for inbound connections was lost. I verified that by host and dig commands.
I found a lost IP on my Network interfaces. I can see that it is still assigned to the correct subnet and has the right interface type network_load_balancer.

My question: How can I return my IP address, or maybe network interface, to my NLB? Do you have any ideas?

已提问 2 年前272 查看次数
1 回答
2
已接受的回答

Is the DNS name that you are looking at with dig configured as an "alias" record in a Route 53 hosted zone? They allow an "evaluate target health" option to be enabled, which automatically removes the IPs from DNS that aren't reporting as healthy.

Particularly if your NLB or the target group is configured not to allow cross-AZ load balancing, the NLB might not have any functioning targets in a given AZ, causing its IP to be removed from DNS. The cross-AZ load balancing option is described in these documentation articles:

专家
已回答 2 年前
专家
已审核 2 年前
  • Hello Leo

    Thank you for your answer. This is exactly what happened to us. Two ECS (faragate) services started in one AZ, and we didn't have cross-zone balancing enabled at our NLB. This is caused by NLB disabling or making inactive one of the IPs.

    This is what the AWS support told us.

    Thank you, Stanislav

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。