2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
~Moving comments out here so they're visible.
Thanks, AC. The sub-domain did work for 5 minutes and now it returning NXDOMAIN again.
that is interesting! You basically have it configured correctly. It works for 5 minutes, and then you get a 'domain does not exist' error after 5 minutes. Do you see this behavior when you try to resolve the FQDN from within the VPC (same VPC that has the load balancer)? What's your TTL?
답변함 2년 전
Eventually, it worked. Thanks
0
In addition to AC's comments, please try the following from https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html
4. Choose the name of the hosted zone that has the domain name that you want to use to route traffic to your load balancer.
5. Choose Create record.
5. Specify the following values:
Routing policy
Choose the applicable routing policy. For more information, see Choosing a routing policy.
Record name
Enter the domain or subdomain name that you want to use to route traffic to your ELB load balancer.
The default value is the name of the hosted zone.
For example, if the name of the hosted zone is example.com and you want to use acme.example.com
to route traffic to your load balancer, enter acme.
Alias
If you are using the Quick create record creation method, turn on Alias.
Value/Route traffic to
Choose Alias to Application and Classic Load Balancer or Alias to Network Load Balancer, then choose
the Region that the endpoint is from.
If you created the hosted zone and the ELB load balancer using the same AWS account – Choose the
name that you assigned to the load balancer when you created it.
If you created the hosted zone and the ELB load balancer using different accounts – Enter the value
that you got in step 1 of this procedure.
Record type
Choose A – IPv4 address.
Evaluate target health
If you want Route 53 to route traffic based on the health of your resources, choose Yes. For more information about checking the health of your resources, see Creating Amazon Route 53 health checks and configuring DNS failover.
7. Choose Create records.
Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your load balancer by using the name of the alias record that you created in this procedure.
답변함 2년 전
Thanks, Sri. I followed those instructions when I created the A record for the sub-domain.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 일 년 전
Is this an internet facing load balancer? If yes, where are you hosting the public domain?
The Application Load Balancer is internet facing and the hosting is public domain. Thanks
thanks! Is the zone file is hosted outside of AWS Route 53? Or are you using Route 53 as the DNS service?
I am using Route53 as the DNS service. There is another sub-domain pointing to CloudFront which works fine, but not the one pointing to ALB. Thanks
Thanks, this is useful. Could you check whether the subdomain delegation is set up correctly? This link explains setting up delegation for a public sub domain: https://aws.amazon.com/premiumsupport/knowledge-center/create-subdomain-route-53/