I am trying to troubleshoot a DNS issue I am currently having with a new project host on an AWS EC2 instance. It is a brand new domain, and I have already updated the nameservers on the registrar side.
It's been a couple days so the new records have propagated. Upon
digging, I have verified the NS records are being correctly pointed to:
; <<>> DiG 9.9.5-3-Ubuntu <<>> creativealchemyhealing.com in NS ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32418 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; QUESTION SECTION: ;creativealchemyhealing.com. IN NS ;; ANSWER SECTION: creativealchemyhealing.com. 172800 IN NS ns-1467.awsdns-55.org. creativealchemyhealing.com. 172800 IN NS ns-364.awsdns-45.com. creativealchemyhealing.com. 172800 IN NS ns-640.awsdns-16.net. creativealchemyhealing.com. 172800 IN NS ns-1551.awsdns-01.co.uk.
NS Records Good. So next i went to verify the A record that I set up in the AWS Hosted Zone is querying correctly to the elastic IP of my EC2 instance:
;; QUESTION SECTION: ;creativealchemyhealing.com. IN A ;; ANSWER SECTION: creativealchemyhealing.com. 300 IN A 188.8.131.52
A Record looks propagated. Excellent.
So then I checked the IP itself to see if that loaded... IP address loads fine: 184.108.40.206.
So why then does the actual domain not query properly? www.creativealchemyhealing.com
What am I missing? Is there a more effective solution to troubleshoot DNS issues other than using the