Gregory's Server
@vkc I've seen a lot of people talk about self-hosting and some amazing tutorials on setting up everything, but I feel like they leave the important part of how are you going to the internet. The DNS part is always left out most of the time. I might be wrong but don't you need a DNS provider if you don't have a static IP. I want to self-host but I get confused on the DNS part, for example, "example. com" can point to a static IP but if your IP changes often, then what to do at that point.
|
4 comments
 @pikachu_sensei @vkc you can use a provider who offers dynamic DNS (ddns) and configure your router to regularly update it. You'll need to open a port in your firewall, and set up a port forwarding rule. If you're using CloudFlare as your name server, you can run a tunnel which will let you mask your IP address behind theirs. They've got a container that works really well for docker compose stacks, DDoS protection, and there's no need to open a port on your router. |
@pikachu_sensei @vkc what you are talking about is "dynamic DNS"( DDNS).
To make this work you will need:
- a domain, hosted somewhere that supports DDNS
- some automated way to check your external IP
- then take that IP and update your DNS record(s) with that IP
Some router manufacures make this easy by giving you a sub-domain under something they own, and built-in functionality to update it.
Some platform providers like linode make it pretty easy to update DNS records via an API call.
I hope the above would at least serve as sufficient info to at least get a sensible search going
@pikachu_sensei @vkc what you are talking about is "dynamic DNS"( DDNS).
To make this work you will need:
- a domain, hosted somewhere that supports DDNS
- some automated way to check your external IP
- then take that IP and update your DNS record(s) with that IP
Some router manufacures make this easy by giving you a sub-domain under something they own, and built-in functionality to update it.