Unusual problem with DDNS connection.
Unusual problem with DDNS connection.
I have an unusual networking problem I’m struggling to fix. Let me try to clarify it. Recently, I purchased a new Asus RT-AX86U Pro Router and a Netgear Modem. On the Jetson Nano I host a Minecraft server and use WireGuard VPN, while on the Raspberry Pi I run Kuma UpTime, which is essentially a custom Docker container that checks my IP address regularly. The situation becomes tricky when I switch devices. First, with the Jetson Nano, WireGuard VPN works perfectly on a remote laptop and Android phone using a custom DDNS address from No-IP. I can easily connect to my VPN without any trouble. But when I try to use the same address for my Minecraft server on a different port, I encounter an error saying "Failed to Connect to the server. Connection timed out: getsockopt." However, using my public IP and the correct port, the Minecraft client connects fine. Now, with the Raspberry Pi, I run a Kuma UpTime webpage and a custom port address. Still, when I access the custom address from No-IP with the specified port, it reports unreachable. This is confusing because my WireGuard VPN works without issues, but my No-IP address doesn’t resolve for the other services either. The ports are open, and port checks show only my real IP, yet the sites still appear to be accessible. I see that my custom DDNS setup in the Asus router also doesn’t seem to help. The ports are configured correctly, and I suspect a DNS resolution problem. Although the DNS server on my router is Quad9, I’ve tried my ISP’s DNS and it didn’t resolve anything. What should I do next? What kind of error am I really facing here? Please help me understand so I can get these services back online. Yes, these three custom ports are indeed forwarded to their respective IoT devices.
Hostnames don’t include port numbers in their records. For instance, you’d use example.ddns.net instead of example.ddns.net:8000. However, the DNS entry remains unchanged—just a different port value. I can run several services from my home using the same ddns.net name but on various ports.
I was entering the address into the client software and then appending the port at the end. example.com:<port number> so I was already doing that, but it still connected no matter what I did. Also, if what you're saying is correct, then clarify why I mentioned that WireGuard functions well with a custom port and address, yet not with other services, even though I'm following the same steps.
It seems there might be more to your configuration than initially thought, possibly involving a reverse proxy. DNS and DDNS can be quite basic—they simply swap your address. If using the IP and port works but not when using the DNS name and port (ensuring the domain resolves correctly), the problem likely lies in the application layer.
It seems WireGuard VPN functions well for your friends while your Minecraft server and website don’t. The same DDNS and port settings are causing issues for you. I’ll reach out to No-IP to check if they can help. Your setup is straightforward, but the Asus RT-ZX86U Pro appears to behave differently.
Did you confirm the accurate IP address during a DNS check for the domain? If it matches, the no-IP function should operate properly. It seems the problem might be connected to Docker or a load balancer you've set up. If the IP works with direct usage but not via the domain name—especially when the domain resolves correctly—then a service like Nginx or Traefik likely depends on the domain for traffic routing.