|
I've been using DynDNS and this automatic update client named BALIDdns for more years than I can recall, suddenly it doesn't work any more - and I discover the DynDNS site (possibly also owners) have changed, this may not be conincidental. Did you silently change the old dyndns protocol (or some aspects of it) which might confuse Bali ? I ca'nt find the technical pages describing the protocol any more. Also, where are the direct URL for individual (respectively, bulk) IP update gone ? I think an updated FAQ would be welcome for everybody's sake. Meanwhile please help - I don't intend to change updaters unless really really necessary. OS=Windows XP and 98. Thanks |
|
You can do a test update using these instructions We have not had any changes to the API in several years, nor would one be made without some sort of documentation/notification. I would suggest following up with Bali in regards to any errors you might be facing with it. Mike Community Manager, Dyn. |
|
Dyn haven't changed anything about the update protocol. Have you checked that your account and hostname still exist? |
|
| We have not had any changes to the API in several years... Ah, OTOH my client's settings haven't changed either and yet it doesn't update properly anymore. §Something/ must have changed, if not the protocol itself, I think, maybe the allowed options ? Specifically I have 3 /free/ host names updated all at once. I'd have to spy the contents of the failing attempts at update, but I fear I could end up blocking my account. Or, might be a problem with wildcard which you, regrattably, removed from free accounts - although I'm almost sure this was some time ago and cared for appropriately. [Edit] According to BaliDDNS's log, the update of the 1st host succeeds, then it hangs forever when updating the second (of 3). This failure is /new/, things worked properly until the 7th of December[ends edit] I have downloaded Dyn's own updater, which works OK in Win XP (but I need a working client for windows 98 too, which yours isn't UIAM). Meanwhile, thanks for the service and your here replies ! New comment : watching BaliDDNS while it is trying to update... Contacting http://dyndns.org server Getting your list of hosts to update ... checking if http://ninho.mine.nu has to be updated This is the error it gets, and locks up ===socket error 10054 (connection reset by peer)=== Any idea what the cause (and remedy) could be, whether at my end or Dyn's ??? Thanks!
Dec 10 at 06:06 PM
Czernobyl
sorry, forgot to add : the first host (ninho.mine.nu) was updated correctly in Dyn's database, the other two of course weren't. Please could you check whether this is a problem with multiple updates in general, or is it just my account (user name : Czernobyl) ? May I do something to ehlp your checking ?
Dec 10 at 06:10 PM
Czernobyl
|
It is not a general problem, because simultaneous updates to multiple (4) hostnames work for me. And because this is merely a user to user forum with staff occasionally stepping by, at least we users can't check account specific problems, of course. |
|
quote Rotblitz:
Thanks. But you may not be using BaliDDNS, probably aren't... The new incompatibility problem that hit me could be with BaliDDNS in "general", or else a "particular" problem with my settings, and then again either settings in my local client or account settings at Dyn's suddenly resulting in requests no more able to be processed. Whatever...
Understood. My point was indeed to see whether the fine staff would check their logs relative to my account. I have new information to pass on : today BaliDDNS update succeeded again for the firts time (since the 7th of December). This happened in Windows 98 which I rarely use now, I'll have to check again what gives under XP. |
1 2 next page »