- 최신
- 최다 투표
- 가장 많은 댓글
As replied to another post of the this same question, the screenshot is not the configuration that is charliehealth.com. From the internet you can see that charliehealth.com nameservers are
;; ANSWER SECTION:
charliehealth.com. 86152 IN NS ns-1935.awsdns-49.co.uk.
charliehealth.com. 86152 IN NS ns-517.awsdns-00.net.
charliehealth.com. 86152 IN NS ns-1043.awsdns-02.org.
charliehealth.com. 86152 IN NS ns-420.awsdns-52.com.
and you screenshot has different ones. Nameservers are registered to charliehealth.com domain at your registrar GoDaddy. You can fix this either by finding the correct Route53 zone that has above nameservers (recommended), or chainging charliehealth.com NS records to point 4 NS in your screeshot (this could potetially break things as the other zone might have different records than yours).
As an example you can check also api.dev.charliehealth.com, this points to elb-shared-us-west-1-47247... in your screenshot but it really is (note the different number after us-west-1-...)
;; ANSWER SECTION:
api.dev.charliehealth.com. 300 IN CNAME elb-shared-us-west-1-48411.aptible.in.
elb-shared-us-west-1-48411.aptible.in. 120 IN A 52.52.108.111
elb-shared-us-west-1-48411.aptible.in. 120 IN A 52.8.19.3
Similary if you now add any new records e.g. foobar.charliehealth.com A 1.2.3.4
you won't be able resolve that either because the zone isn't the one that is true charliehealth.com :-( I hope you can find the correct zone from one of your AWS accounts.
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전