R2 Help
Hi Cloudflare Team,
I'm currently using QUIC.cloud nameservers for my domain and I'd like to start offloading my media content to an R2 bucket. However, I want to avoid changing my existing nameserver and DNS settings if possible.
Currently, I'm using a subdomain (r2.dev) for my R2 bucket. Is there a way to configure Cloudflare to serve media from my R2 bucket while keeping my QUIC.cloud nameservers and current DNS records intact?
#r2
3 Replies
hi i am facing r2 issue Issue any one have know what is the issue Description:
We are experiencing intermittent DNS resolution issues with our Cloudflare R2 endpoint:
https://mydomain.73aeaf32da92cb026419738a2b442d0e.r2.cloudflarestorage.com.
Error Details:
Error: A server with the specified hostname could not be found. (NSURLErrorDomain Code=-1003)
Affected users receive this error sporadically, while it works fine for others.
Troubleshooting Steps Taken:
Verified DNS resolution using nslookup—no apparent issues.
Confirmed that the R2 bucket and object permissions are correctly configured.
Checked that the signed URLs (X-Amz-* parameters) are valid and not expired.
Observed the issue across different ISPs and regions, with no clear pattern.
Request for Assistance:
We would appreciate any guidance on resolving this intermittent DNS issue or insights into potential misconfigurations on the Cloudflare R2 endpoint.
Hey Akash, one option that I can think of is setting up a Worker to access the files.
Is the problem resolved? Can you please open a separate thread?
Hey, i have a problem, removing a bucket and a custom domain, enrolled with cloud connector R2 feature. I am not very techy and i dont know how to create a worker to serve media from the bucket, but i supposed that the application i host on the website i tryed to serve images from, has already implemented something that will work on the back-end to do the job, because the app: Xilancer, has a plugin that integrates the cloud storage feature, with a front-end GUI, where you need to input cloudflare bucket, URL, API key and the secret key... and i assumed it does the job ... but it seems it is not, because i am unable to access the domain now anymore,i get an 401 error. When i tried to remove the domain and the bucket i was unable do to that cloud connector, where i am unable to delete that connection... it misses that feature.