|
First, please pardon me if I'm not being clear with my technical wording and thanks a million to those who try to help. I've been a very satisfied free customer for a while but am now experiencing a phenomenon that I can't seem to fix! My DynDNS hostname isn't working because the IP address reverts to my router IP address. When I go to the Modify Hostname page, the IP address is usually 192.168.x.x yet right below it says "Your current location's IP address is" my correct modem IP address. This phenomenon began when my ISP (Verizon) sent a new modem that had a router attached. I bridged the modem so it would work with my NETGEAR WNR834B v2 router which is also attached to a D-link DNS-323 NAS box with FTP capability. Also with the addition of the new modem was a new assignment of internal IP addresses by the router beginning with 10.0.0.x. Finally, I can access the NAS box from outside my network by using my real IP address. Port forwarding has also been implemented on the router. I think I've included everything I know about this situation. Does anyone know why DynDNS can't hold my external IP address? I must have something misconfigured. Thanks again. |
The question has been closed Oct 29 at 09:13 PM ago by RotBlitz for the following reason "Abandoned question".
|
Ah, it sounds like your new modem is not bridged, but is still routing. If it was bridged then your old router wouldn't be getting that 192.168.x.x address. The problem isn't that DynDNS isn't "holding" your external IP address, but that your router is reporting the IP address it is being given by the modem/router. You have a few choices:
Jun 25 at 05:51 PM
RotBlitz ♦
|
|
I'm having this same problem with my DVR for my camera security system. I have the update client software, and my router has a built in updater. The only thing though is that I don't want my dyndns hostname IP's address to be my router's, I want it to be my DVR's. How can I do this? You see that you posted a question in the answer section, do you?
Oct 29 at 09:12 PM
RotBlitz ♦
|