this post was submitted on 17 Jun 2023
10 points (91.7% liked)
Selfhosted
60409 readers
1036 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just sign up for cloud flare, you will change your name servers after you set it up, but they walk you through that.
Hi, could you explain the concept behind having to change my nameservers? Thanks
Currently your web address has a domain that is forwarded to your lemmy instance. After setting up cloudlflare, you wil have to switch it to cloudflare's nameservers. They will cdn/host/protect files and part of your site will come from there to users, and the rest will come from your server.
Thanks for your comment! Could you tell me why Cloudflare would need for me to use their nameservers to protect my site and proxy traffic through their infrastructure to my instance? I'm very curious about the technical reason for them to ask us to do so
Well if the nameservers went just to your instance, they couldn't provide anything. That address only goes to that machine. To use the cloudflare service, traffic goes there first, then to your instance. Think of a nameserver as an adress. If the content is at your house, then going straight to your house is what you're doing now. There's no wat for cloudflare to get in the middle.
Thank you. I'm trying to understand how exactly is using CF's nameservers letting Cloudflare intercept traffic from around the world to my instance?
When you type a TLD into the internet, a nameserver tells where that address is. Right now it's going to your instance, to work, cloudlfare needs to be the address. Cloudflare isnt something you install on your server, it's a nother server.
If Cloudflare just needed the address, they could query the domain name I would provide them during the setup process (which they do, in order to set up the CDN). Why their DNS servers instead of my own?
My apologies, I think I'm missing a crucial point here which is why I'm asking the same question multiple times. Thanks so much for your help!