One perk that someone told me about is that you can use your domain to get around not having a static IP (because the DNS will compensate).
If I were to get a Cloudflare domain name then what would be some other pros and cons?
One perk that someone told me about is that you can use your domain to get around not having a static IP (because the DNS will compensate).
If I were to get a Cloudflare domain name then what would be some other pros and cons?
You’d need to implement Dynamic DNS to update the records. DNS alone won’t do that.
There are docker containers that auto update cloudflare a records for dynamic IP.
Is there a guide I can follow? Currently I’m using dynv6 and have a bash script that updates my ipv6 every 10 mins or so.
Correct. I used NOIP for years until I realized that 1) my IP address is static and 2) my home IP address was being exposed. (Pretty obvious I know but sometimes I am slow on the uptake 😃)
My solution was to get a $5 per month vps and reverse proxy and reverse ssh tunnels.
The $5 / month VPS ($60/year) was pretty much the cost of NOIP per year to use custom domains.
I just use duckdns as a free dynamic IP service. But you are correct about it exposing your home IP. Personally I’m not concerned about that so it works for me. Then I use Apache to route my incoming traffic depending on subdomain.
Might as well use a Cloudflare tunnel.
Yeah, Cloudflare tunnel takes care of the dynamic DNS. It has limitations, which is why I switched to Caddy and Nginx, but Cloudflare is relatively easy to set up for n00bs and I highly recommend it.
Adds latency and now Cloudflare sees all your traffic