2

I am trying setting up a small HTTP Server visible from the internet using DynamicDNS.

As DynDNS Service I'm using DuckDNS.org. I set up the DynamicDNS service on my router and the IPs (on my router and on DuckDns) are up to date so I assume it's working.

I then set up the port forwarding from the router to my computer (Running Linux and Apache) and everything seems ok.

The website works using the DynDNS domain only when I'm using my local connection. I can see my web page and everything works fine. When i try to access it using a different connection (Like 4G on my phone) the domain seems to not respond and even if I try to ping the public ip of the router (or the dyndns domain) the request times out.

I can't understand what is the problem: have I misunderstood the principle behind the connection? Or is it some sort of firewall thing?

Any help is really appreciated. Thanks in advance :)

Improve this question
3
  • 1
    Try manually the Duck DNS update URL that you programmed on the router to see its full answer. Add &verbose=true to the request for more information.
    – harrymc
    Commented Jul 28, 2019 at 9:30
  • Make certain you have e.g. Listen 80 (i.e. not Listen 1.2.3.4:80) in your httpd.conf. Likewise, make certain the virtual host for your dynamic DNS website starts with <VirtualHost *:80> not e.g <VirtualHost 1.2.3.4:80>.
    – Anaksunaman
    Commented Jul 28, 2019 at 10:21
  • I'm trying to do the same thing, in germany with vodafone internet... and yes there is some kind of nat(called DS-Lite here), but I read that using ipv6 it is doable, however it didn't work for me with v6 as well... did you figure out how to do that?
    – Parsa
    Commented Apr 14 at 18:02

2 Answers 2

Reset to default
1

You don't have a route-able public ip address on your router, probably your router is behind NAT. you can't use ddns service in this situation. you must buy or rent a public address from your service provider if is possible.

Improve this answer
3
  • I think this could be the problem. I did some research and some other people with my ISP have the same problem too. Is there any way to resolve this thing without buying a static IP? Like for example, if I call my isp are they able to make me bypass the NAT?
    – LeonardoA
    Commented Jul 28, 2019 at 21:40
  • Most stable way is to buy a public ip address from your service provider, but yes there are some other ways for example using same vpn tunnel service with different private ipaddresses on your client and your server then you can access your private vpn address on your server from your client but you must try different vpn services to find if it's possible or not, because on some vpn services it's not possible. for bypassing NAT I'm not sure if it's possible or not.
    – Rasool Ziafaty
    Commented Jul 29, 2019 at 17:01
  • If my answer was the answer for your question you can accept it as correct one.
    – Rasool Ziafaty
    Commented Jul 29, 2019 at 17:03
1

you could try pinging the DDNS address using a terminal or command prompt when you ping it, it should say pinging (your public IP) (Atleast on windows). Also,make sure to forward a port on your router that leads to the Ipv4 address of the computer running the https server?

Improve this answer
1
  • Pinging the ddns address on cmd gives me the right IP address (the router one) so at least the ddns service an its updating are working. Anyway, even if the address resolves, the ping request times out. I'm not sure whether I have or not forwarded a port for https (the 443 one I think?): I'll check but, as I was trying to connect using http I don't think that much would change. Thanks anyway :D
    – LeonardoA
    Commented Jul 30, 2019 at 13:57

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .