CasaOS y DuckDNS son servicios que ayudan a gestionar dominios y configuraciones de red.
CasaOS y DuckDNS son servicios que ayudan a gestionar dominios y configuraciones de red.
Hello, I just set up Casa on my Raspberry Pi and downloaded the DuckDNS app to make it reachable outside my internal network. When I added the subdomain and token details from the DuckDNS website into the app’s configuration, I encountered a bad gateway error. I’m not very comfortable with Linux or Docker setup, so I’m unsure what might be wrong. Any suggestions or steps you could try would be greatly appreciated. Thanks!
I aim to clarify your intentions by asking about the specific goal. Are you planning to set up a publicly accessible DNS server? Did you modify any router settings to enable this? It’s important to confirm whether your internet service provider allows such activity, as it’s generally not common for consumers.
Hi, sorry for the confusion. I realized I should have begun there. My idea was that DuckDNS would give you a subdomain linked to your regularly updated public IP. With tools like Nextcloud, you could just use a domain instead of managing port forwarding. CasaOS functions more like Docker with a graphical interface, and I'm experimenting with setting up additional services such as Nextcloud or Calibre Server locally. In my mind, once the DuckDNS app was set up, it would direct to the subdomain, allowing me to reach CasaOS outside my network. However, I haven't found many resources covering DuckDNS in detail, especially for this particular setup. Thanks for your response. Edit: I located a GitHub page for the LinuxServer/duckdns Docker image on Docker Hub.
A domain name lets you avoid managing the constantly changing IP address, using a stable name instead. This works separately from port forwarding, which is required to expose services behind your router to the internet. Your domain points to your public IP, which belongs to your ISP's router. Consequently, any request to that IP will typically go through your router and be blocked unless you configure it otherwise. To make a service accessible publicly, set up port forwarding so that traffic directed to a specific port reaches a device on your network. Regarding the Duck DNS Updater, it automatically updates your domain whenever your public IP changes, ensuring the name always resolves to your current IP. I haven't encountered any information suggesting it functions as a reverse tunnel for automatic exposure.
The information on the store page isn't clear about whether it's merely an updater.
It defines the full range of its capabilities. The initial sentences in its descriptions convey the main idea clearly. It aligns with the app's about page: https://www.duckdns.org/about.jsp. Essentially, it modifies a DNS entry to direct traffic to your present IP address. Your decisions on forwarding and opening ports remain under your control.
I'm feeling really confused right now! Thanks for your time. Have a great day.