gatorback
New Member
BACKGROUND
About 8 years ago, I had setup ZoneEdit to provide DDNS for a .com and .us domain in the same account. DDNS was working well for both until a few months ago. The .us domain continues to work, however, the problem is with the .com domain. Now that I have a little time, I would like to understand what the issue. Excerpt from tail /tmp/syslog.log:
OBSERVATIONS
I have intentionally set the .com DNS entry to 8.8.8.8 in zoneedit, with the goal to have the DDNS client to update to the WAN (Internet) IP address. I was unable to find any differences in the settings of the .com and .us settings, that could cause the error. I updated my router to the latest firmware, and attempted to use the token authentication and account password authentication.
Line 5 and 7 of the log entry indicates that communication is occurring between the router and ZoneEdit.
QUESTIONS
How can the Error in Line 6 of the log be used to diagnose the problem?
Is there a terminal command that can dump useful diagnostic data that could be posted (pastebin)?
I have command line access (SSH) to the DDNS client.
Thank you for actionable suggestions / diagnostic questions.
About 8 years ago, I had setup ZoneEdit to provide DDNS for a .com and .us domain in the same account. DDNS was working well for both until a few months ago. The .us domain continues to work, however, the problem is with the .com domain. Now that I have a little time, I would like to understand what the issue. Excerpt from tail /tmp/syslog.log:
- Sep 2 09:04:48 ddns update: asusddns_update: 1
- Sep 2 09:05:14 watchdog: start ddns.
- Sep 2 09:05:14 rc_service: watchdog 481:notify_rc start_ddns
- Sep 2 09:05:14 ddns update: ez-ipupdate: starting...
- Sep 2 09:05:14 ddns update: connected to dynamic.zoneedit.com (64.68.198.48) on port 80.
- Sep 2 09:05:19 ddns update: error processing request
- Sep 2 09:05:19 ddns update: server output: HTTP/1.1 200 OK^M Date: Wed, 02 Sep 2015 13:05:15 GMT^M Server: Apache/2.2.22 (Debian)^M X-Powered-By: PHP/5.4.35-0+deb7u2^M Set-Cookie: easydns_language=en_US; expires=Thu, 01-Sep-2016 13:05:15 GMT; path=/^M Set-Cookie: PHPSESSID=ohpbriu78vvb2dn9nu1q0u0cr3; path=/^M Expires: Thu, 19 Nov 1981 08:52:00 GMT^M Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0^M Pragma: no-cache^M Vary: Accept-Encoding^M Content-Length: 98^M Connection: close^M Con
OBSERVATIONS
I have intentionally set the .com DNS entry to 8.8.8.8 in zoneedit, with the goal to have the DDNS client to update to the WAN (Internet) IP address. I was unable to find any differences in the settings of the .com and .us settings, that could cause the error. I updated my router to the latest firmware, and attempted to use the token authentication and account password authentication.
Line 5 and 7 of the log entry indicates that communication is occurring between the router and ZoneEdit.
QUESTIONS
How can the Error in Line 6 of the log be used to diagnose the problem?
Is there a terminal command that can dump useful diagnostic data that could be posted (pastebin)?
I have command line access (SSH) to the DDNS client.
Thank you for actionable suggestions / diagnostic questions.
Last edited:
