Comment 4 for bug 116066

I do not have, or use, ddclient. What I did was a wget members.dyndns.com... and it timed out. Ping succeeded, but it does not provide much data or worth. In fact, 'telnet members.dyndns.com 80', followed by "get / HTTP/1.0" and some hits of the Return key would work as a pretty good test. But... telnet is unable to open a session there...

Please note that ping uses ICMP, while this is a TCP connection; by pinging, all we know is that this host (or someone posing as this host) is alive; it does not follow that an HTTP server is running and accepting connections at this address (members.dyndns.com at port 80).

bug 60159 is not the same: there we have a "no route to host" error; here we have a time out.

Right now this would more appropriately be taken with DynDNS support.