Ah. Makes sense. I don’t think you have to specifically use cloudflare in that case. But I remember CNAME records can’t be used for everything… there are some limitations. I know I had issues with dyndns and a domain at some point. I just can’t remember the details. I know it didn’t work with every registrar / DNS provider. But some of them offer some magic to make some things work. I believe back then we ended up transferring that domain to some other hoster. And my domains are with a company that offers an API. I can just have a small script that changes around entries and do dyndns that way. But obviously you remember that records have a certain time to live and you want to set it correctly for your use-case.
Comment on How I accidentally slowed down my nextcloud instance for months
Swarfega@lemm.ee 7 months agoI don’t have a static IP but host services off my paid domain. I use duckdns and point host records to the duckdns address. I have to use CloudFlare to manage my DNS records for this to work.
rufus@discuss.tchncs.de 7 months ago
Swarfega@lemm.ee 7 months ago
The CNAME flattening is not a regular feature of DNS, so I have to use Cloudflare. Maybe other providers do the same, but I haven’t looked around. It’s certainly not something namecheap offer.
I point my TLD to the dynamic DNS record and then point to other records to the TLD as CNAME records. I’m using Nginx Proxy Manager to reverse proxy traffic to different services. These all live on a Raspberry Pi 4.
rufus@discuss.tchncs.de 7 months ago
Swarfega@lemm.ee 7 months ago
Awesome info! I wasn’t overly happy with having to use CloudFlare for just this one feature. I’ll have a test with my registrar.
capital@lemmy.world 7 months ago
I do the same but I just use a script that runs periodically to update CloudFlare with my current IP with their native API.