- 最新
- 投票最多
- 评论最多
Hello.
"elb.amazonaws.com" is a domain managed by AWS, so you should not be able to create and access a subdomain from this domain.
If there is a possibility that you can connect, try setting the host header using the curl command as shown below.
ALB's host-based routing probably looks at the host header and sorts the connections, so if you set the host header, you may be able to connect.
curl -H 'Host:test.test-alb-XXXXXXXXX.us-east-1.elb.amazonaws.com' test-alb-XXXXXXXXX.us-east-1.elb.amazonaws.com
If the ALB name is 'test-alb-XXXXXXXXX.us-east-1.elb.amazonaws.com', then that is the default name you need to access it with, not a sub-domain e.g. 'test.test-alb-XXXXXXXXX.us-east-1.elb.amazonaws.com.'. Change your listener rule to not match on any Host header, but to unconditionally forward to your target group.
I see you had an NXDOMAIN - that is because your client could not resolve 'test.test-alb-XXXXXXXXX.us-east-1.elb.amazonaws.com.'. ALB DNS matching the ALB name is added to DNS for you, but not a sub-domain 'test'.
相关内容
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前