|
I can not access from my home comp. and i have been able to before. How do i get it to work again. |
|
This wiki might be able to help troubleshooting this. If you need further assistance, you certainly must provide more details than just "I cannot access from my home comp". |
|
I believe something is wrong at DynDNS, or something has begun blocking access to the DynDNS updating service: As of Thursday, March 4, I have seen several systems that had been working properly for as long as 3 or 4 years or more suddenly unable to update. (Friends, colleagues, clients, & even some of my own!) The Update Client sends the update to DynDNS as usual, but DynDNS doesn't update to the new IP and the remote users are unable to connect any longer. NONE of them have received any e-mail about abuse, so that apparently is not the issue. In most cases, they are using the router's DDNS, and that seems to now be failing after working for a long time. Using the DynDNS Software Update Client solved some of them (so, again, they obviously weren't blocked for abuse), but didn't solve it for all. This also isn't a practical solution for all installations, since the IP change sometimes takes place when the computer with the Update software is powered off & the IP doesn't get updated. And no-one is onsite to power up the computer. These are remote installations (the reason they are using DDNS in the first place. In my own case, I was able to use the Update Client in one location, since the PC stays on all the time. In another location, I had to switch to another DDNS supplier (No-IP.com) because the router had to do the updating, and the router IP updates resumed immediately on changing to No-IP after they hadn't updated in 4 days with DynDNS. I think this is a system problem at DynDNS, or at least something they should be looking into. NOTE THAT I went through all the Troubleshooting WIKI's and Support Sites and the solutions were not there. In addition, all units had been working flawlessly up until Thursday March 04/2010. |
|
It would have been better to open your own thread instead of stepping in here. Sorry, thought it was germaine, going by the date & the issue being the same (working fine, then not working). Please check your host list, RotBlitz, & see if your router DDNS has updated since March 4 (your IP may not have changed in the meantime, so you wouldn't experience the problem yet in that case). Please let us know here, in case it is a problem reaching DynDNS or at DynDNS??? --FB
Mar 08 at 11:04 PM
Fraser-Bell
Well, my ISP disconnects at least every 24 hours. I have the choice of the hour, so I selected 4-5am. This is also when my IP address always changes, and the router changes reliably and immediatly my hostname's IP address via DDNS update, since months until this morning without any interruption. As I have also Dynamic DNS Pro, I also can see the updates in my update log, currently back until March 4. You see - not a general problem, else it wouldn't work for me either.
Mar 08 at 11:28 PM
RotBlitz ♦
Thanks, needed to know that. Problem then is somewhere between the affected systems/update clients and DynDNS. Perhaps one (or two) of the large IPs (Bell, Shaw) have added even more new choking and blocking in their pipeline! You have helped. Thanks -FB
Mar 09 at 11:22 AM
Fraser-Bell
UPDATE: I was correct in the first place. Problem has been fixed by DynDNS.
Mar 11 at 09:35 AM
Fraser-Bell
|