Hi there !
I have an issue with ddns updater installed on a syno DS211.
Today I could not access my NAS from external anymore, I was getting the error "The server is temporarily unable to service your request
due to maintenance downtime...Please try again later", without knowing exactly whether this was coming from the DNS provider (OVH and dyndns in my case), from my bbox at home, or from the NAS (which I have updated with the latest DSM 4.0 2228 yesterday.
Looking closer today, what I see is that my current public IP is 109.129.205.51
Where on dyndns web site, it refers to "188.40.176.106 " as my public IP (I guess it is the same on OVH, but I do not know how to check on their web site what the current public IP is registered there)
Looking at ddns updater on my NAS, I do see that the last update to ddns and ovh was successfully done on 4/07 with adress 109.129.205.51, see log below :
it looks very strange to me, as my current IP is 109.129.205.51, which is the one ddns updater sent on 16:59.
Later on in the day, ddns updater sent IP 188.40.176.106, which is not my current one, my current one being 109.129.205.51, and on the ddns updater, the IP which is showned as sent is 109.129.205.51
So I am pretty sure there is a bug here ... see printscreen below :
I have an issue with ddns updater installed on a syno DS211.
Today I could not access my NAS from external anymore, I was getting the error "The server is temporarily unable to service your request
due to maintenance downtime...Please try again later", without knowing exactly whether this was coming from the DNS provider (OVH and dyndns in my case), from my bbox at home, or from the NAS (which I have updated with the latest DSM 4.0 2228 yesterday.
Looking closer today, what I see is that my current public IP is 109.129.205.51
Where on dyndns web site, it refers to "188.40.176.106 " as my public IP (I guess it is the same on OVH, but I do not know how to check on their web site what the current public IP is registered there)
Looking at ddns updater on my NAS, I do see that the last update to ddns and ovh was successfully done on 4/07 with adress 109.129.205.51, see log below :
Rich (BBCode):
Jul 5 18:56:54 ddclient[17094]: INFO : service started
Jul 5 18:56:50 ddclient[13611]: INFO : service stopped
Jul 4 20:50:02 ddclient[13611]: INFO : service started
Jul 4 20:49:24 ddclient[12983]: INFO : service started
Jul 4 20:45:58 ddclient[]: ERROR : during exec of offline-script ''
Jul 4 20:45:58 ddclient[]: INFO : executing offline-script ''
Jul 4 20:45:57 ddclient[]: INFO : offline mode activated, redirect to ip: 188.40.176.106
Jul 4 20:45:57 ddclient[28982]: SUCCESS: updating synospace.dyndns.org: good: IP address set to 188.40.176.106
Jul 4 20:45:57 ddclient[28982]: SUCCESS: updating xxx.dyndns.org: good: IP address set to 188.40.176.106
Jul 4 20:45:56 ddclient[28982]: SUCCESS: updating xxx.be: good: IP address set to 188.40.176.106
Jul 4 20:44:07 ddclient[10933]: INFO : service stopped
Jul 4 16:59:53 ddclient[10933]: SUCCESS: updating synospace.dyndns.org: good: IP address set to 109.129.205.51
Jul 4 16:59:53 ddclient[10933]: SUCCESS: updating xxx.dyndns.org: good: IP address set to 109.129.205.51
Jul 4 16:59:53 ddclient[10933]: SUCCESS: updating xxx.be: good: IP address set to 109.129.205.51
it looks very strange to me, as my current IP is 109.129.205.51, which is the one ddns updater sent on 16:59.
Later on in the day, ddns updater sent IP 188.40.176.106, which is not my current one, my current one being 109.129.205.51, and on the ddns updater, the IP which is showned as sent is 109.129.205.51
So I am pretty sure there is a bug here ... see printscreen below :