03-22-2005 09:33 AM - edited 03-09-2019 10:42 AM
I am using an 831 router and am trying to get DDNS to work. Here is the debug output:
RESS_ASSIGN: Interface Ethernet1 assigned DHCP address 67.162.204.242, mask 255.255.254.0, hostname testlab831.xxxxxx.com
00:53:06: DYNDNSUPD: Adding DNS mapping for testlab831.xxxxxxxx.com <=> 67.162.204.242
00:53:06: DYNDNSUPD: Sleeping for 3 seconds waiting for interface Ethernet1 configuration to settle
00:53:09: HTTPDNS: Update add called for testlab831.xxxxxxxx.com <=> 67.162.204.242
00:53:09: HTTPDNS: Update called for testlab831.xxxxxxxx.com <=> 67.162.204.242
00:53:09: HTTPDNS: init
00:53:09: HTTPDNSUPD: Session ID = 0x4
00:53:09: HTTPDNSUPD: URL = '<A HREF="javascript:newWin('http://xxxxx:xxxx@members.dyndns.org/nic/update?system=dyndns&hostname=testlab831.xxxx.com&myip=67.162.204.242')">http://xxxxx:xxxx@members.dyndns.org/nic/update?system=dyndns&hostname=testlab831.xxxx.com&myip=67.162.204.242</A>'
00:53:09: HTTPDNSUPD: Sending request
00:53:29: HTTPDNSUPD: Call returned Connection time out for update testlab831.xxxxxx.com <=> 67.162.204.242
00:53:29: HTTPDNSUPD: Freeing response
00:53:29: DYNDNSUPD: Another update completed (outstanding=0, total=0)
00:53:29: HTTPDNSUPD: Clearing all session 4 info
I am curious what the problem is with the "Call returned Connection time out for update testlab831.xxxxxx.com <=>" line.
Does my syntax look correct?
03-28-2005 11:26 AM
Do you have some kind of authorization in place ?
03-28-2005 12:24 PM
The authorization is in the HTTP:// string.
I found out that the problem is with the firewall settings that get enabled when you use the web interface. It set up such a restrictive set of access-lists the response wasn't being received from the web server. Once I pulled the access-list of interface the update worked. This is a really nice feature!
05-06-2011 12:37 PM
Hello !
Our System has DDNS update problems like this:
(...) HTTPDNSUPD: URL = 'http://user:password@members.dyndns.org/nic/update?system=dyndns&hostname=labXXX.dyndns.org&myip=61.xxx.xxx.xxxpassword@members.dyndns.org/nic/update?system=dyndns&hostname=labXXX.dyndns.org&myip=61.xxx.xxx.xxx'
(...) HTTPDNSUPD: Sending request
(...) HTTPDNSUPD: Call returned Connection time out, update of labXXX.dyndns.org <=> 61.xxx.xxx.xxx failed
(...) DYNDNSUPD: Another update completed (outstanding=0, total=0)
... joking log entries "Another update completed" after "Call retruned Conection time out".
Our System is a "CISCO1921-SEC" with IOS 15.1(3)T1. We configured zone-based-firewall rules included the self-zone. The outgoing policy-map "self-WAN" has no restrictions (tcp, upd, icmp), the incomming policy-map "WAN-self" was also reduced to even the same - everything may enter with "tcp, udp or icmp".
In other dicussion threads some access-list changings solved the problem. But in this case - I don't see any access-lists between "self" and "WAN" (to be updated) or the way back.
We also read the message on the dnydns page - in this case we are not using https - but it should work also with http !?
Please, if you have an idea ... ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide