ddns not updating Cisco C827 w/ 12.4.23

kvieyra12 · ‎03-19-2009

The only error shown in the debug is "DATA START 404" see below.

Everything else is working as desired, all my internet traffic is passing thru this router now.

But, I see when I check my services at dyndns.org that the ip has not been updated.

Someone must have gotten this feature working, Any suggestions?

I have also attached my config (with a passwords and usernames changed:)

Kevin

ADSL#

*Mar 12 06:45:51.178: DYNDNSUPD: Adding DNS mapping for mydomain.homeip.net <=> 64.229.179.83 server 63.208.196.95

*Mar 12 06:45:51.178: HTTPDNS: Update add called for mydomain.homeip.net <=> 64.229.179.83

*Mar 12 06:45:51.182: HTTPDNSUPD: Session ID = 0xC

*Mar 12 06:45:51.182: HTTPDNSUPD: URL = '<A HREF="javascript:newWin('http://myname:pas...@members.dyndns.org/nic/update&hostname')">http://myname:pas...@members.dyndns.org/nic/update&hostname</A>= mydomain.homeip.net&myip=64.229.179.83'

*Mar 12 06:45:51.186: HTTPDNSUPD: Sending request

*Mar 12 06:45:51.354: HTTPDNSUPD: Response for update mydomain.homeip.net <=> 64.229.179.83

*Mar 12 06:45:51.358: HTTPDNSUPD: DATA START 404 <----- HERE is the problem,,,,,

*Mar 12 06:45:51.358: HTTPDNSUPD: DATA END, Status is Response data recieved, successfully

*Mar 12 06:45:51.358: HTTPDNSUPD: Call returned SUCCESS, update of mydomain.homeip.net <=> 64.229.179.83 succeeded

*Mar 12 06:45:51.362: DYNDNSUPD: Another update completed (outstanding=0, total=0)

*Mar 12 06:45:51.366: HTTPDNSUPD: Clearing all session 12 info

ADSL#

Richardsma · ‎03-19-2009

Don't know if this is the cause but in your config you have the following..

ip ddns update method DynDNS

HTTP

add pas...@members.dyndns.org/nic/update%3Fsystem')">http://mylogon:pas...@members.dyndns.org/nic/update%3Fsystem=

Between "update" and "system" you have "%3F" where you should have a "?"

To add a ? to a config you need to do CTRL + V first.

As I said, I'm not sure if this is the cause of your issue but worth a try.

kvieyra12 · ‎03-19-2009

Yes, I have since changed that. I was hoping someone would recognize that 404 error. I did see a suggestion that it was too long a password being sent to dyndns.org. But, I have also shortened mine to 5 characters.