Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using zoneedit and my ddclient doesnt seem to work. Running the following command:
ddclient -daemon=0 -debug -verbose -noquiet
gives me this error even after I try a day later.
RECEIVE: <ERROR CODE="702" PARAM="600" TEXT="Minimum 600 seconds between requests" ZONE="....com">
FAILED: updating t...com: 702: Minimum 600 seconds between requests
my ddclient conf:
Code:
daemon=600 # check every 300 seconds
syslog=yes # log update msgs to syslog
mail=root # mail all msgs to root
mail-failure=root # mail failed update msgs to root
pid=/var/run/ddclient.pid # record PID in file.
ssl=yes # use ssl-support. Works with
# ssl-library
#
#use=watchguard-soho, fw=192.168.111.1:80 # via Watchguard's SOHO FW
#use=netopia-r910, fw=192.168.111.1:80 # via Netopia R910 FW
#use=smc-barricade, fw=192.168.123.254:80 # via SMC's Barricade FW
#use=netgear-rt3xx, fw=192.168.0.1:80 # via Netgear's internet FW
#use=linksys, fw=192.168.1.1:80 # via Linksys's internet FW
#use=maxgate-ugate3x00, fw=192.168.0.1:80 # via MaxGate's UGATE-3x00 FW
#use=elsa-lancom-dsl10, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router
#use=elsa-lancom-dsl10-ch01, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router
#use=elsa-lancom-dsl10-ch02, fw=10.0.0.254:80 # via ELSA LanCom DSL/10 DSL Router
#use=alcatel-stp, fw=10.0.0.138:80 # via Alcatel Speed Touch Pro
#use=xsense-aero, fw=192.168.1.1:80 # via Xsense Aero Router
#use=allnet-1298, fw=192.168.1.1:80 # via AllNet 1298 DSL Router
#use=3com-oc-remote812, fw=192.168.0.254:80 # via 3com OfficeConnect Remote 812
#use=e-tech, fw=192.168.1.1:80 # via E-tech Router
#use=cayman-3220h, fw=192.168.0.1:1080 # via Cayman 3220-H DSL Router
#
#fw-login=admin, fw-password=XXXXXX # FW login and password
#
## To obtain an IP address from FW status page (using fw-login, fw-password)
#use=fw, fw=192.168.1.254/status.htm, fw-skip='IP Address' # found after IP Address
#
## To obtain an IP address from Web status page (using the proxy if defined)
#use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address
#
#use=ip, ip=127.0.0.1 # via static IP's
#use=if, if=eth0 # via interfaces
#use=web # via web
#
#protocol=dyndns2 # default protocol
#proxy=fasthttp.sympatico.ca:80 # default proxy
#server=members.dyndns.org # default server
#server=members.dyndns.org:8245 # default server (bypassing proxies)
#login=your-login # default login
#password=test # default password
#mx=mx.for.your.host # default MX
#backupmx=yes|no # host is primary MX?
#wildcard=yes|no # add wildcard CNAME?
##
## dyndns.org dynamic addresses
##
## (supports variables: wildcard,mx,backupmx)
##
# server=members.dyndns.org, \
# protocol=dyndns2 \
# your-dynamic-host.dyndns.org
##
## dyndns.org static addresses
##
## (supports variables: wildcard,mx,backupmx)
##
# static=yes, \
# server=members.dyndns.org, \
# protocol=dyndns2 \
# your-static-host.dyndns.org
##
##
## dyndns.org custom addresses
##
## (supports variables: wildcard,mx,backupmx)
##
# custom=yes, \
# server=members.dyndns.org, \
# protocol=dyndns2 \
# your-domain.top-level,your-other-domain.top-level
##
## ZoneEdit (zoneedit.com)
##
pid=/var/run/ddclient.pid
protocol=zoneedit1
use=web, web=dnspark
server=dynamic.zoneedit.com
login=xxxx
password=xxxx
mysite.com
What am i doing wrong?
Also anyway to let ddclient auto update every hour or so?
I don't see a section where you check for your external/dynamic IP address. Try adding the following:
Code:
#
## To obtain an IP address from Web status page (using the proxy if defined)
## by default, checkip.dyndns.org is used if you use the dyndns protocol.
## Using use=web is enough to get it working.
## WARNING: set deamon at least to 600 seconds if you use checkip or you could
## get banned from their service.
#use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address
use=web, web=ipdetect.dnspark.com/, web-skip='Current Address:'
#
I don't see a section where you check for your external/dynamic IP address. Try adding the following:
Code:
#
## To obtain an IP address from Web status page (using the proxy if defined)
## by default, checkip.dyndns.org is used if you use the dyndns protocol.
## Using use=web is enough to get it working.
## WARNING: set deamon at least to 600 seconds if you use checkip or you could
## get banned from their service.
#use=web, web=checkip.dyndns.org/, web-skip='IP Address' # found after IP Address
use=web, web=ipdetect.dnspark.com/, web-skip='Current Address:'
#
The error is usually caused by ddclient trying to update zoneedit too frequently with the same IP address. I don't currently use zoneedit but in the past when I did use zoneedit they blocked update attempts if they happened too frequently.
One of the potential causes of ddclient trying to update zoneedit every 600 seconds is an incomplete /var/cache/ddclient/ddclient.cache file. What I've done in the past is manually change the cache file to contain the correct IP address and restart ddclient. This allows ddclient to continue to check for IP address changes and allow enough time to pass so zoneedit no longer blocks updates.
The error is usually caused by ddclient trying to update zoneedit too frequently with the same IP address. I don't currently use zoneedit but in the past when I did use zoneedit they blocked update attempts if they happened too frequently.
One of the potential causes of ddclient trying to update zoneedit every 600 seconds is an incomplete /var/cache/ddclient/ddclient.cache file. What I've done in the past is manually change the cache file to contain the correct IP address and restart ddclient. This allows ddclient to continue to check for IP address changes and allow enough time to pass so zoneedit no longer blocks updates.
Hi
When I checked the cache file the ip address is already there. How can I do like you say not update every 600 seconds? and if the ip address is already correct to ignore it?
This is my cache file:
Code:
# last updated at Tue Oct 11 09:25:00 2016 (1476174300)
atime=1476174300,backupmx=0,custom=0,host=mysite.com,ip=xxx.xxx.xxx.xxx,mtime=1476173942,mx=,static=0,status=failed,warned-min-error-interval=0,warned-min-interval=0,wildcard=0,wtime=0 mysite.com
SENDING: GET / HTTP/1.0
SENDING: Host: ipdetect.dnspark.com
SENDING: User-Agent: ddclient/3.7.3
SENDING: Connection: close
SENDING:
RECEIVE: HTTP/1.1 200 OK
RECEIVE: Server: nginx
RECEIVE: Date: Tue, 11 Oct 2016 15:29:48 GMT
RECEIVE: Content-Type: text/html; charset=UTF-8
RECEIVE: Connection: close
RECEIVE: Current Address: xx.xx.xx.xx
DEBUG: get_ip: using web, http://ipdetect.dnspark.com/ reports xx.xx.xx.xx
Use of uninitialized value in string ne at /usr/local/sbin/ddclient line 2033.
SUCCESS: mysite.com: skipped: IP address was already set to xx.xx.xx.xx.
Still no idea why its not autoupdating.
Looks good here assuming xx.xx.xx.xx are the same from dnspark and zoneedit. The "uninitiated value" warnings are normal when the IP does not need updating.
You got your current IP address back from dnspark and zoneedit said success your IP is already set. Is there something else you're expecting or I'm missing?
Looks good here assuming xx.xx.xx.xx are the same from dnspark and zoneedit. The "uninitiated value" warnings are normal when the IP does not need updating.
You got your current IP address back from dnspark and zoneedit said success your IP is already set. Is there something else you're expecting or I'm missing?
Hi Chuck
I changed my ip address in zonedit and ran the verbose to check if its updating and it says the same thing ip skipped already set..
I was hoping once i set a false ip in zoneedit and test ddclient it would reset it to the correct ip but it failed.. now i am actually completey screwed lol, i did something and i cant login using ssh or login with root account says root account disabled if i just login via ftp using root... ssh is completely not working..
debug1: identity file /root/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /root/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3p1 Debian-1
ssh_exchange_identification: read: Connection reset by peer
I changed my ip address in zonedit and ran the verbose to check if its updating and it says the same thing ip skipped already set..
That's not how it works. It checks your current IP address against the local cache that contains the last successful update of zoneedit. If the IP address in the cache is unchanged and it hasn't hit an update threshold set in the config file then it waits until the next check. It assumes your not changing zoneedit manually or with another program.
You could use the -force option to force an update of zoneedit in your use case.
That's not how it works. It checks your current IP address against the local cache that contains the last successful update of zoneedit. If the IP address in the cache is unchanged and it hasn't hit an update threshold set in the config file then it waits until the next check. It assumes your not changing zoneedit manually or with another program.
You could use the -force option to force an update of zoneedit in your use case.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.