Hello, The domain futureapi.com is always shows an error - Check DNS Configuration. I have made sure that the DNS configuration is correct in AWS Route 53. Route 53 config - www .futureapi.com. = competent-wing-xxxxx.netlify.com futureapi.com = dns1.p06.nsone.net to dns4.p06.nsone.net Also, …

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 …

Hi @jen Thank you so much for the reply. 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 IPV…

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 d…

Hi @gregraven , Thank you so much for the reply. 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 d…

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…

@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.…

Thank you for the details. I have made the following changes right now- added A record for futureapi(dot)com to point to the Netlify load balancer. CNAME of www points to the netlify subdomain. Changed back the NS values back to AWS NS (ex- ns-407(dot)awsdns-50(dot)com. etc.,) Let me know if the…

You’re making progress; your site is starting to load for me. The “dig” values look correct, too.

Thank you for your time and sharing details as to what had to be done. Everything seems to work right now.

Brilliant work, @gregraven ! @futureapi , glad you’re all set for now- please reach out again if you have any other questions down the road.

Check DNS Configuration in Netlify Dashboard

Support

jen May 2, 2020, 6:40pm 2

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?

Topic		Replies	Views
DNS verification failed www.taskoo.in doesn't appear to be served by Netlify Support netlify-dns-https-ssl , netlify-newbie	8	2251	May 18, 2020
SSL Certificate error "net::ERR_CERT_COMMON_NAME_INVALID" Support netlify-dns-https-ssl	7	1308	September 11, 2023
Error: Let’s Encrypt certificate for your custom domain Support netlify-dns-https-ssl	3	237	March 5, 2024
DNS verification failed www.ruck.gg doesn't appear to be served by Netlify Support netlify-dns-https-ssl	4	709	March 3, 2020
Did Netlify’s load balancer IP address change? Support deployment , netlify-dns-https-ssl	11	2917	February 21, 2023

Check DNS Configuration in Netlify Dashboard

Related topics