CLIFFS: why would a remote connection work using direct ip, but not with a dyndns domain when the domain is resolving to the correct ip?
using some camera monitoring software to login remotely and view cameras. this is not really the issue
the issue is that the network im logging into via internet has a dynamic ip and i am therefore using dyndns service with dyndns updater
for a day or so, dyndns worked just fine
now when i try to connect im getting a connection failure. dyndns updater is updating correctly, i tested it. pinging the dyndns address from the remote computer yields the right ip. but it wont connect
if i try to connect to the ip directly, it works just fine
port forwarding is also required but that is setup fine too
the basic question is, why would a connection work with direct ip, but not with a dyndns domain when the domain is resolving to the correct ip?
Zippy
using some camera monitoring software to login remotely and view cameras. this is not really the issue
the issue is that the network im logging into via internet has a dynamic ip and i am therefore using dyndns service with dyndns updater
for a day or so, dyndns worked just fine
now when i try to connect im getting a connection failure. dyndns updater is updating correctly, i tested it. pinging the dyndns address from the remote computer yields the right ip. but it wont connect
if i try to connect to the ip directly, it works just fine
port forwarding is also required but that is setup fine too
the basic question is, why would a connection work with direct ip, but not with a dyndns domain when the domain is resolving to the correct ip?
Zippy