- Newest
- Most votes
- Most comments
Your screenshot is not the zone that is serving charliehealth.com !!!
$ dig NS charliehealth.com
...
;; ANSWER SECTION:
charliehealth.com. 172800 IN NS ns-1043.awsdns-02.org.
charliehealth.com. 172800 IN NS ns-1935.awsdns-49.co.uk.
charliehealth.com. 172800 IN NS ns-420.awsdns-52.com.
charliehealth.com. 172800 IN NS ns-517.awsdns-00.net.
But you have different name servers in your screenshot. So those are not the records you are looking for ;-)
Dear user,
DNS can always be tricky, but I might need some more information about your environment.
But first I need to check one thing:
- I cannot find a CNAME entry for links.charliehealth.com but multiple A entries which resolve fine: https://www.whatsmydns.net/#A/links.charliehealth.com
- You write that you want to configure a subdomain but mention a CNAME record. Did you specify the CNAME record in the zone charliehealth.com ?
- Some customer run split-DNS configurations. Can you check if the hosted zone where your created the outreach CNAME record is a public hosted zone and it is reaching the right AWS account, e.g. by comparing the NS entries?
Thank you!
Here are screenshot of the dns records: https://ibb.co/YDhr3hC
- Interesting, not sure why that would be.
- Yes
- It is a public hosted zone. The rest of the setup is and has been working properly as far as I can tell. Which entires should I be comparing?
Chaining CNAME in general isn't considered as "best-practice" but it does work like your example of www.charliehealth.com proves.
;; ANSWER SECTION:
www.charliehealth.com. 2791 IN CNAME proxy-ssl.webflow.com.
proxy-ssl.webflow.com. 60 IN CNAME proxy-ssl-geo.webflow.com.
proxy-ssl-geo.webflow.com. 60 IN A 34.251.201.224
proxy-ssl-geo.webflow.com. 60 IN A 34.253.101.190
proxy-ssl-geo.webflow.com. 60 IN A 54.194.170.100
Without being able to see how your Route53 records are, the only guess I could come up with was this
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#CNAMEFormat
if you create a CNAME record for a subdomain, you cannot create any other records for that subdomain. For example, if you create a CNAME for www.example.com, you cannot create any other records for which the value of the Name field is www.example.com.
Hello and thanks!
I updated my question with a link to a screenshot of the records.
In the docs you link above it also states: "You cannot create a CNAME record for example.com, but you can create CNAME records for www.example.com, newproduct.example.com, and so on."
I think it's saying I cannot create www.outreach.charliehealth.com--unless I am misunderstanding
Relevant content
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hello, could you explain this a little more? My screenshot is the only zone that I have and it is for charliehealth.com. What records should I be looking for?
If you look at the NS records (nameservers) returned for "dig NS charliehealth.com" above and compare those to your screenshot those are not the same. This is something that was setup when you (or someone) did register charliehealth to .com -domain at GoDaddy (that seems to be registrar for the domain charliehealth.com). Would that help in finding the root cause?