Related

Tool Instant DNS Lookup Tool Tool
Why China to Singapore bypass Los Angeles ? Question Question
TXT records using Digital Ocean DNS not working Question Question

Question

Cloudflare 1001 error when digital ocean URL redirect is available in nslookup for domain URL

Posted February 8, 2021 118 views
DNS

Hi,
I have set up a website using a standard account and a static site. I followed the instructions to point the registrar (www) CNAME record to the digital ocean URL. A nslookup of the domain URL returns a redirect to digital ocean URL (which is accessible) but on trying to access domain URL I keep on getting Cloudflare 1001 error. This has been going on for a couple of hours. Is this a DNS propogation issue or some other problem? If a DNS propagation issue, how long will it take to resolve in Cloudflare?
TIA.

Add a comment
vinniesingh
By:
vinniesingh

Related

Tool Instant DNS Lookup Tool Tool
Why China to Singapore bypass Los Angeles ? Question Question
TXT records using Digital Ocean DNS not working Question Question
Add a comment
1 comment
  • jdd1489 February 8, 2021
    Show comment This comment has been marked as resolved by jdd1489.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer
jdd1489 February 9, 2021

I just had this issue and resolved it.

This was my setup and if it matches what you’re trying to achieve, consider trying the solution below.

I had my DNS nameservers pointing to and managed by digitalocean.
My app requires only wildcard subdomains to point to the app platform, *.mydomain.com, and NOT the root domain mydomain.com.

I created a CNAME record that points *.mydomain.com to EXAMPLE-APP.ondigitalocean.app.

This produced the Cloudflare Error 1001 page for any subdomain I attempted to vist.

SOLUTION

I found pointing my nameservers away from DigitalOcean and to Cloudflare solved my problem.
Create a free Cloudflare account, import the domains DNS records, and change the Nameservers to the ones they provide.

Make sure that the CNAME record pointing to the app platform DOES NOT have an orange cloud next to it. It needs to be DNS only.

After that verify your Cloudflare SSL settings are set to Full. I found using Full (Strict) would give me a certificate error when visiting my subdomains.

I hope this helps!

Reply Report
  • vinniesingh February 13, 2021

    Thanks for your comment and your help. I was doing something wrong. I was trying to use the nameservers by godaddy to point to my app using CNAME which didn’t work due to the value of the A records in godaddy. I started using digital ocean nameservers and this resolved the issue.

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help