Also, I wanted to set futureapi.com as the primary domain, which didn’t work out because of the above issue.
And now the Lets encrypt SSL certificate is throwing an error in the Netlify dashboard- SniCertificate::CertificateInvalidError: Unable to verify challenge for futureapi(dot)com
Hey @futureapi, sorry you’re running into this my hunch is that you have an existing IPv6 record that’s conflicting with the A record pointing to our load balancer. Similar issue to here:
Could you see if that’s the case and, if so, delete that record at AWS and see if it solves this problem for you?
I checked my config on AWS Route 53. I don’t see any A record for the domain futureapi.com.
As mentioned above in the post above, I just have 2 configs. One a CNAME for www and the other is a NameServer configs from values dns1 to dns4.
I don’t see an IPV6 record there in Route53.
Something does seem to be weird with your DNS. I see you have the four Netlify DNS name servers set up, but while they return A return a “Netlify” IP address, otherwise the A record shows as being with AWS.
First question: Why is AWS Route 53 involved? You should be able to make entries with your domain registrar that point to the Netlify DNS name servers and eliminate the middleman. Am I correct is thinking that you registered your site with NameCheap?
Second question: If you’re trying to assign DNS to Netlify from the DNS at Route 53, why do you have a CNAME entry? With Netlify as your DNS, you shouldn’t have other DNS entries at other services that might conflict, right?
Reg. First Question:
I am using Route 53 as I’m using couple of AWS services to host the product(like lambda, ec2, RDS etc.,).
I love Netlify and prefer Netlify to host static sites, so, I wanted to host my homepage here.
Yes, you are right. My domain registrar is NameCheap.
Reg. Second Question:
I was instructed(during configuring the website) by netlify to have CNAME entry for www.futureapi.com and have NS entries for futureapi.com. Is there anything else I have to do or try?
Do you suggest me to delete the CNAME record? Will that be ok?
Please let me know if I have to try something to get this to work.
You just need to figure out what service you want to have handling your DNS, as any of these three (NameCheap, Route 53, Netlify) can handle those duties. But you need to pick one and have all your DNS setup there.
In your position, here’s what I would try:
Tell NameCheap that you are using Route 53 for DNS, and then make each of your DNS entries there. In Route 53, you would have an A record for Netlify’s load balancer, plus the CNAME entry for your Netlify subdomain (e.g. futureapi.netlify.app).
The only DNS entries I would have in Netlify are those mandated by Netlify to point the Netlify subdomain (futureapi.netlify.app) to the custom domain (futureapi.com).
@gregraven
Yes, that sounds reasonable. That’s exactly how it is routed right now. But, there is a missing piece though.
I have not pointed A record to Netlify’s A record. According to this article - Configure external DNS for a custom domain | Netlify Docs
It says, I have to point it to 104.198.14.52. So, adding a new A record to 104.198.14.52 should fix the issue right?
If AWS supports CNAME flattening, then I believe you can add another CNAME for your www subdomain. Cloudflare supports CNAME flattening, but usually you cannot have a CNAME for an apex domain name, which in your case is futureapi.com.
If not, you should add an A record to the Netlify load balancer 104.198.14.52. Even if AWS supports CNAME flattening, this should get you on track.
For what it’s worth, I’m still showing that you have Netlify defined as the name server for your custom domain, not AWS. If I understand your setup correctly, you will want to use AWS name servers, and with AWS specify the A and CNAME records for your Netlify hosting for this website. That is, you would NOT have entries for Netlify name servers within AWS, but rather let AWS handle the propagated DNS.
my hunch is that you have an existing IPv6 record that’s conflicting with the A record pointing to our load balancer. Similar issue to here: