DDNS Updater Not updating the public IP to 2 dns providers ...

Status
Für weitere Antworten geschlossen.

fa355115

Benutzer
Mitglied seit
29. Jan 2012
Beiträge
27
Punkte für Reaktionen
0
Punkte
0
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 :

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 :

ddns.jpg
 

QTip

Super-Moderator
Teammitglied
Mitglied seit
04. Sep 2008
Beiträge
2.341
Punkte für Reaktionen
13
Punkte
84
hi,

there is a function to connect to a offline ip, if the ds shutdown. The page that display the offline message are on my server, pre configured in the ddns updater and freely provided for the user.
It seems your ds shutdown at 20:44:07 and refreshed all ddns to 188.40.176.106. After the ds started again the old cache would be restored, but no log entry was written.

If you not wish to connect to an offline ip if the ds shutdown, then go to the options dialog and clear the field "offline ip".
If you have a own offline ip (not offline url), then you can enter it in this field.

you are using an old v1.19, a v1.20 are out for some days.
 
Zuletzt bearbeitet:

fa355115

Benutzer
Mitglied seit
29. Jan 2012
Beiträge
27
Punkte für Reaktionen
0
Punkte
0
Qtip,

You are helping me a lot ... but I still need to understand some things.
This is the error message I am getting - can you please confirm to me it is the one you are talking about which is coming from your server ?

serveur.jpg ?

Now, I need to better understand what happens, and I have 2 questions :

1. I am now out on vacation and trying to access my home network through my domain .... but I am getting again this error message. So it looks to me like ddns updater still didnt update the OVH nor DYNDNS with my new public IP which most probably recently changed again. Assuming the new public IP wasn't sent by ddns updater to OVH and DYNDNS, it means OVH and DYNDNS still know about my old public IP ... and in such case, it is normal they return to this screen I pasted above (Which I understand is on your own server ?!?) ?

2. On the problem itself, why is ddns updater not updating my providers with the new ublic IP ?
The log I pasted in the first post is related to the installation of the latest DSM on my NAS ... so I could understand the ddns updater service was maybe not properly functionning anyore ... but at the moment I am writing those lines, I have the problem again (I can't access my NAS through my domain). What is the issue here ?
 
Zuletzt bearbeitet:

fa355115

Benutzer
Mitglied seit
29. Jan 2012
Beiträge
27
Punkte für Reaktionen
0
Punkte
0
Qtip,

You are helping me a lot ... but I still need to understand some things.
This is the error message I am getting - can you please confirm to me it is the one you are talking about which is coming from your server ?

Anhang anzeigen 9120 ?

Now, I need to better understand what happens, and I have 2 questions :

1. I am now out on vacation and trying to access my home network through my domain .... but I am getting again this error message. So it looks to me like ddns updater still didnt update the OVH nor DYNDNS with my new public IP which most probably recently changed again. Assuming the new public IP wasn't sent by ddns updater to OVH and DYNDNS, it means OVH and DYNDNS still know about my old public IP ... and in such case, it is normal they return to this screen I pasted above (Which I understand is on your own server ?!?) ? I mean this "old public adress" could now be assigned to someone else, so how is it possible you "own it" and this adress links to this error message now ?

2. On the problem itself, why is ddns updater not updating my providers with the new ublic IP ?
The log I pasted in the first post is related to the installation of the latest DSM on my NAS ... so I could understand the ddns updater service was maybe not properly functionning anyore ... but at the moment I am writing those lines, I have the problem again (I can't access my NAS through my domain). What is the issue here ? Can you please help me investigating what the issue is and ddns updater was not able to send the new adress to OVH and Dyndns ? I am on vacation now but I have asked so to reset my BBOX tonight so that I have access again and I can give you some log ...

Hope you can give me an udate as soon as possible - many thanks for this !
 

QTip

Super-Moderator
Teammitglied
Mitglied seit
04. Sep 2008
Beiträge
2.341
Punkte für Reaktionen
13
Punkte
84
1. I am now out on vacation and trying to access my home network through my domain .... but I am getting again this error message. So it looks to me like ddns updater still didnt update the OVH nor DYNDNS with my new public IP which most probably recently changed again. Assuming the new public IP wasn't sent by ddns updater to OVH and DYNDNS, it means OVH and DYNDNS still know about my old public IP ... and in such case, it is normal they return to this screen I pasted above (Which I understand is on your own server ?!?) ?
This page is the offline page from my server, which is has the ip 188.40.176.106.
A few months ago I changed the behavior after restarting the ds due to frequent reboots, the ddns host were blocked. I only moved the previous saved cache file with the old ip's and dont update the ddns hosts to prevent abuse. If the ip dont change to often you have a good chance that it would work, but if the offline mode active, there is no chance to function after reboot. Now I must confess that this was a thinking error and i'll changed it in the next version.
2. On the problem itself, why is ddns updater not updating my providers with the new ublic IP ?
The log I pasted in the first post is related to the installation of the latest DSM on my NAS ... so I could understand the ddns updater service was maybe not properly functionning anyore ... but at the moment I am writing those lines, I have the problem again (I can't access my NAS through my domain). What is the issue here ?
Does your DS shutdown every day at a specificm time?
If you cleared the field "offline ip" and your ddns hosts have still the wrong ip, you can do the follwing:

  • stop ddnsupdater
  • log into shell as root
  • cd to /tmp/cache/ddclient/
  • open ddclient.cache in edit mode and remove alle entries under the top comment fields # (don't delete the ddclient.cache)
  • save the modified ddclient.cache
  • start ddnsupdater, you see ? sign on every host
  • after a few seconds all hosts have the correct ip
 

fa355115

Benutzer
Mitglied seit
29. Jan 2012
Beiträge
27
Punkte für Reaktionen
0
Punkte
0
QTIP,

For sure this issue occurs every time my server reboots.
The 2 first times was after a DSM update.
Yesterday was because I indtalled the "Mail station" package, and I remember now the the server also rebooted.

Now, I'd like to know more about the issue.

1. You say : "This page is the offline page from my server, which is has the ip 188.40.176.106." ... I have a question on this. do you mean this adress "188.40.176.106" is your own adress ? I mean earlier in this post, I saw this adress as my "Public adress" on dyndns web site ... so I ws thinking this was an "old" public adress of my ISP provider which was recently changed but not updated by ddns updater on OVH and Dyndns. So in other worsd, is this really an adress from you which you use each time you need (offline mode), and are you sending it to my OVH and Dyndns ? I thought this was a public adress which was assigned to my by my ISP then "updated", as my ISP does every 96 hours I think.

2. Still about the issue ... why is ddns updater not sending the "current public IP" after a DS reboot ?? Each time I have a DS reboot, I have the issue that ddns updater is not sending the current Public IP to my providers (OVH, Dyndns).

3. Do I understand correctly that as a "thinking error" (As you say below), you developped something that takes the public IP which was there before the DS reboots and puts it in cache as public adress to be used after the DS has finished to reboot and send it to OVH, etc ... ?

This is still unclear to me, but ne thing is sure, is that the problem occurs each time my DS reboots, where it would be so easy to read the current public IP after a DS reboot to send it to OVH, etc ...

Please note the public IP in my case comes from my BBOX, and not from the DS, which is behind the BBox.
Rebooting the BBox makes it receiving a new Public IP, recognized by the DS, and managed by DDns updater ...


P.S. : Here is the log showing again what happened when my DS rebooted on "Jul 14 13:02:27"

Jul 16 18:14:20 ddclient[11417]: SUCCESS: updating synospace.dyndns.org: good: IP address set to 109.129.172.167
Jul 16 18:14:20 ddclient[11417]: SUCCESS: updating cedricdelecole.dyndns.org: good: IP address set to 109.129.172.167
Jul 16 18:14:20 ddclient[11417]: SUCCESS: updating cedricdelecole.be: good: IP address set to 109.129.172.167
Jul 16 18:13:35 ddclient[9831]: NOCONNECT: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'
Jul 16 18:13:35 ddclient[9831]: NOCONNECT: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'
Jul 16 18:13:34 ddclient[9831]: NOCONNECT: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'
Jul 14 13:05:57 ddclient[11417]: INFO : service started
Jul 14 13:05:04 ddclient[9831]: INFO : service started
Jul 14 13:02:58 ddclient[]: ERROR : during exec of offline-script ''
Jul 14 13:02:58 ddclient[]: INFO : executing offline-script ''
Jul 14 13:02:57 ddclient[]: INFO : offline mode activated, redirect to ip: 188.40.176.106
Jul 14 13:02:57 ddclient[30441]: SUCCESS: updating synospace.dyndns.org: good: IP address set to 188.40.176.106
Jul 14 13:02:57 ddclient[30441]: SUCCESS: updating cedricdelecole.dyndns.org: good: IP address set to 188.40.176.106
Jul 14 13:02:57 ddclient[30441]: SUCCESS: updating cedricdelecole.be: good: IP address set to 188.40.176.106
Jul 14 13:02:54 ddclient[]: INFO : service stopped
Jul 14 13:02:27 ddclient[24578]: INFO : service stopped
Jul 13 19:26:28 ddclient[24578]: SUCCESS: updating synospace.dyndns.org: good: IP address set to 109.129.31.169
Jul 13 19:26:28 ddclient[24578]: SUCCESS: updating cedricdelecole.dyndns.org: good: IP address set to 109.129.31.169
Jul 13 19:26:26 ddclient[24578]: SUCCESS: updating cedricdelecole.be: good: IP address set to 109.129.31.169

Many Thanks !
 

QTip

Super-Moderator
Teammitglied
Mitglied seit
04. Sep 2008
Beiträge
2.341
Punkte für Reaktionen
13
Punkte
84
QTIP,

1. You say : "This page is the offline page from my server, which is has the ip 188.40.176.106." ... I have a question on this. do you mean this adress "188.40.176.106" is your own adress ? I mean earlier in this post, I saw this adress as my "Public adress" on dyndns web site ... so I ws thinking this was an "old" public adress of my ISP provider which was recently changed but not updated by ddns updater on OVH and Dyndns. So in other worsd, is this really an adress from you which you use each time you need (offline mode), and are you sending it to my OVH and Dyndns ? I thought this was a public adress which was assigned to my by my ISP then "updated", as my ISP does every 96 hours I think.
Yes, 188.40.176.106 is my ip.
ok, let me explain:
On shutdown the DS, a script stop ddns updater and move the current cache file into a save place in the ddnsupdater dir. After that a special offline config (a copy of yours with the given offline ip) are used, to update all of your hosts with the offline ip. If the DS online again the previous moved cache are copied back to /tmp/cache/ddclient and used. Your host at dyndns still have the offline ip. The ddnsupdater checks on start and verify the ip in the cache against the actual public ip, not with the stored ip at dyndns!. So your current public ip are actual in ddnsupdater, but not at dyndns. As long as the public ip does not change, ddnsupdater will not notice a change. Do you understand the problem?

what did i do for the next release:
i change the code, that if offline mode active (ip in field "offline ip") the offline config are used and the ddnsupdater see a change between the offline ip and your current public ip. if offline mode not active, the original cache were used. If a ip change happend durring the ds are offline, ddnsupdater notice this and changed the ip to your current public ip.
If you reboot to often, it is better you deactivate the offline mode by clearing the field "offline ip". A nightly shutdown and morning restart should not abuse your hosts, i think. But if your reboot many times in a short time, better deactivate offline mode.
 

fa355115

Benutzer
Mitglied seit
29. Jan 2012
Beiträge
27
Punkte für Reaktionen
0
Punkte
0
Yes, 188.40.176.106 is my ip.
ok, let me explain:
On shutdown the DS, a script stop ddns updater and move the current cache file into a save place in the ddnsupdater dir. After that a special offline config (a copy of yours with the given offline ip) are used, to update all of your hosts with the offline ip. If the DS online again the previous moved cache are copied back to /tmp/cache/ddclient and used. Your host at dyndns still have the offline ip. The ddnsupdater checks on start and verify the ip in the cache against the actual public ip, not with the stored ip at dyndns!. So your current public ip are actual in ddnsupdater, but not at dyndns. As long as the public ip does not change, ddnsupdater will not notice a change. Do you understand the problem?

what did i do for the next release:
i change the code, that if offline mode active (ip in field "offline ip") the offline config are used and the ddnsupdater see a change between the offline ip and your current public ip. if offline mode not active, the original cache were used. If a ip change happend durring the ds are offline, ddnsupdater notice this and changed the ip to your current public ip.
If you reboot to often, it is better you deactivate the offline mode by clearing the field "offline ip". A nightly shutdown and morning restart should not abuse your hosts, i think. But if your reboot many times in a short time, better deactivate offline mode.

1. Yes, If I understad well, upon restart of the DS, the ddns updater should have compared the actual Public IP with the one on OVH and Dyndns, not with the one in cache (correct ?)

2. From what realease have you modified the code ?

3. What is the purpose of the "Offline ip" mode ? Is it just to display this "error" message, or ... ?
In my case, I do not really care about having this message or not. All I want is to have the ddns updater checking the current Public IP with the one stored on OVH and Dyndns (And update it if needed) every time the NAS is rebooting.

P.S. : I am rebooting my NAS quite rarely ...

Thanks to advise.
 
Status
Für weitere Antworten geschlossen.
 

Kaffeautomat

Wenn du das Forum hilfreich findest oder uns unterstützen möchtest, dann gib uns doch einfach einen Kaffee aus.

Als Dankeschön schalten wir deinen Account werbefrei.

:coffee:

Hier gehts zum Kaffeeautomat