| [windows hosting] Longtime DynDNS User, but Having Troubles Late I have been using DynDNS since about 2005 when I switched over from cable to DSL service and have been hosting my web pages on my Windows XP-based server all these years.
This evening, I got an error that is persistent and won't clear with a reboot:
Winsock error 11001 (Host not found). All of my web sites are offline as a result.
My domains are hosted with Namecheap and I noticed Namecheap seems to have a dynamic DNS capability of its own, but each time I have tried to set it up, it doesn't work. And it seems that one must set up a separate instance and password for every domain, meaning one would have to run a copy of their DNS updater utility for every web domain, which would be cumbersome.
Presently, I just run the DynDNS Updater, one instance, and it handles all my domains because each web is a subdomain on the server. A Google search on the topic indicates that others are unable to get Namecheap's dynDNS to work either.
I was considering upgrading to static IP (presently I do a 'what is my IP' every few hours and just log into Namecheap and update the IP address that each domain points to, but this is cumbersome and can't be done remotely if I'm out of town), but I checked the AT&T website and there is only DSL Elite, which is dynamic IP only. I'm currently on their 3m/512k package, dynamic IP. U-verse is not available in my area.
Has anyone gotten Namecheap's dynDNS to actually work, and if so, how do you set it up, step by step? Their vague online tutorial doesn't go into troubleshooting why it doesn't connect. |
