Hi, does anyone have a similar issue or a solution to mine?
I have set up a Dynamic DNS for Dynv6 service on my 192.168.1.2 OpenWrt dumb AP / switch (so I had to use URL for obtaining the IP, as the dumb AP does not have a wan interface and a public IP). I manage to set it up the way that the system log does not show any error message and the DDNS service looks like it "successfully" sends and verifies the IP and info to Dynv6. However, Dynv6 does not get the updates.
I don't know if the problem is on the OpenWrt side or the Dynv6 side. However, taken that the forum on Dynv6 is pretty much dead and I have never had a problem with their service (from a main router), I assume the OpenWrt forum is more suitable for this question.
Again, it seems to get a verification (so the API and login info seems to be correct... when not set up properly, there is an error in system log), but it does not really gets it through to the dynv6 server.
You are probably correct, I missed this – I changed it to br-lan, but still the same – it seems to verify everything right, but no update on the dynv6 server.
The dynv6 log is following:
233921 : ************ ************** ************** **************
233921 note : PID '3505' started at 2023-05-01 23:39
233921 : ddns version : 2.8.2-37
233921 : uci configuration:
ddns.dynv6.check_unit='minutes'
ddns.dynv6.domain='DOMAIN.dynv6.net'
ddns.dynv6.enabled='1'
ddns.dynv6.force_unit='minutes'
ddns.dynv6.interface='br-lan'
ddns.dynv6.ip_source='web'
ddns.dynv6.ip_url='http://checkip.amazonaws.com'
ddns.dynv6.lookup_host='DOMAIN.dynv6.net'
ddns.dynv6.password='***PW***'
ddns.dynv6.retry_unit='seconds'
ddns.dynv6.service_name='dynv6.com'
ddns.dynv6.use_ipv6='0'
ddns.dynv6.use_syslog='2'
ddns.dynv6.username='none'
ddns.dynv6=service
233921 : verbose mode : 0 - run normal, NO console output
233921 : check interval: 600 seconds
233921 : force interval: 4320 seconds
233921 : retry interval: 60 seconds
233921 : retry max count : 0 times
233921 : No old process
233921 : last update: never
233921 : Detect registered/public IP
233921 : #> /usr/bin/host -t A DOMAIN.dynv6.net >/var/run/ddns/dynv6.dat 2>/var/run/ddns/dynv6.err
233922 : Registered IP 'IP-ADDRESS' detected
233922 info : Starting main loop at 2023-05-01 23:39
233922 : Detect current IP on 'web'
233922 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv6.dat -o /var/run/ddns/dynv6.err --no-proxy 'http://checkip.amazonaws.com'
233922 : Current IP 'IP-ADDRESS' detected on web at 'http://checkip.amazonaws.com'
233922 : Forced Update - L: 'IP-ADDRESS' == R: 'IP-ADDRESS'
233922 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv6.dat -o /var/run/ddns/dynv6.err --no-proxy 'http://dynv6.com/api/update?hostname=DOMAIN.dynv6.net&token=***PW***&ipv4=IP-ADDRESS'
233924 : DDNS Provider answered:
addresses unchanged
233924 info : Forced update successful - IP: 'IP-ADDRESS' send
233924 : Waiting 600 seconds (Check Interval)
234924 : Detect registered/public IP
234924 : #> /usr/bin/host -t A DOMAIN.dynv6.net >/var/run/ddns/dynv6.dat 2>/var/run/ddns/dynv6.err
234924 : Registered IP 'IP-ADDRESS' detected
234924 info : Rerun IP check at 2023-05-01 23:49
234924 : Detect current IP on 'web'
234924 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv6.dat -o /var/run/ddns/dynv6.err --no-proxy 'http://checkip.amazonaws.com'
234924 : Current IP 'IP-ADDRESS' detected on web at 'http://checkip.amazonaws.com'
234924 : Waiting 600 seconds (Check Interval)
235924 : Detect registered/public IP
235924 : #> /usr/bin/host -t A DOMAIN.dynv6.net >/var/run/ddns/dynv6.dat 2>/var/run/ddns/dynv6.err
235925 : Registered IP 'IP-ADDRESS' detected
235925 info : Rerun IP check at 2023-05-01 23:59
235925 : Detect current IP on 'web'
235925 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv6.dat -o /var/run/ddns/dynv6.err --no-proxy 'http://checkip.amazonaws.com'
235925 : Current IP 'IP-ADDRESS' detected on web at 'http://checkip.amazonaws.com'
235925 : Waiting 600 seconds (Check Interval)
000925 : Detect registered/public IP
000925 : #> /usr/bin/host -t A DOMAIN.dynv6.net >/var/run/ddns/dynv6.dat 2>/var/run/ddns/dynv6.err
000926 : Registered IP 'IP-ADDRESS' detected
000926 info : Rerun IP check at 2023-05-02 00:09
000926 : Detect current IP on 'web'
000926 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv6.dat -o /var/run/ddns/dynv6.err --no-proxy 'http://checkip.amazonaws.com'
000926 : Current IP 'IP-ADDRESS' detected on web at 'http://checkip.amazonaws.com'
000926 : Waiting 600 seconds (Check Interval)
001926 : Detect registered/public IP
001926 : #> /usr/bin/host -t A DOMAIN.dynv6.net >/var/run/ddns/dynv6.dat 2>/var/run/ddns/dynv6.err
001926 : Registered IP 'IP-ADDRESS' detected
001926 info : Rerun IP check at 2023-05-02 00:19
001926 : Detect current IP on 'web'
001926 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv6.dat -o /var/run/ddns/dynv6.err --no-proxy 'http://checkip.amazonaws.com'
001927 : Current IP 'IP-ADDRESS' detected on web at 'http://checkip.amazonaws.com'
001927 : Waiting 600 seconds (Check Interval)
Interesting. It seems that it does communicate with dynv6. Does it mean that if it detects the same IP on the web interface (e.g. the Amazon URL IP check) and the DDNS server, then it does not update it and does not send the instruction to the dynv6 server? From what I remember, it always used to send the instruction, even if the IP still matched the one on the DDNS server.
This is not an issue (and it would end up as an error message in the system log). The DDNS has scripts for specific DDNS services. option service_name 'dynv6.com' is one of them and it contains the http link for the DDNS message. There is no difference between this script and if I specify it straight in the DDNS config file without specifying the service_name.
The log file from the DDNS settings with the direct link:
004931 : ************ ************** ************** **************
004931 note : PID '9178' started at 2023-05-02 00:49
004931 : ddns version : 2.8.2-37
004931 : uci configuration:
ddns.dynv62.check_unit='minutes'
ddns.dynv62.domain='DOMAIN.dynv6.net'
ddns.dynv62.enabled='1'
ddns.dynv62.force_unit='minutes'
ddns.dynv62.ip_source='web'
ddns.dynv62.ip_url='http://checkip.amazonaws.com'
ddns.dynv62.lookup_host='DOMAIN.dynv6.net'
ddns.dynv62.password='***PW***'
ddns.dynv62.retry_unit='seconds'
ddns.dynv62.update_url='http://dynv6.com/api/update?hostname=[DOMAIN]&token=[PASSWORD]&ipv4=[IP]'
ddns.dynv62.use_ipv6='0'
ddns.dynv62.use_syslog='2'
ddns.dynv62.username='none'
ddns.dynv62=service
004931 : verbose mode : 0 - run normal, NO console output
004931 : check interval: 600 seconds
004931 : force interval: 4320 seconds
004931 : retry interval: 60 seconds
004931 : retry max count : 0 times
004931 : No old process
004931 : last update: never
004931 : Detect registered/public IP
004931 : #> /usr/bin/host -t A DOMAIN.dynv6.net >/var/run/ddns/dynv62.dat 2>/var/run/ddns/dynv62.err
004931 : Registered IP 'IP' detected
004931 info : Starting main loop at 2023-05-02 00:49
004931 : Detect current IP on 'web'
004931 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv62.dat -o /var/run/ddns/dynv62.err --no-proxy 'http://checkip.amazonaws.com'
004932 : Current IP 'IP' detected on web at 'http://checkip.amazonaws.com'
004932 : Forced Update - L: 'IP' == R: 'IP'
004932 : #> /usr/bin/wget --hsts-file=/tmp/.wget-hsts -nv -t 1 -O /var/run/ddns/dynv62.dat -o /var/run/ddns/dynv62.err --no-proxy 'http://dynv6.com/api/update?hostname=DOMAIN.dynv6.net&token=***PW***&ipv4=IP'
004932 : DDNS Provider answered:
addresses unchanged
004932 info : Forced update successful - IP: 'IP' send
004933 : Waiting 600 seconds (Check Interval)
It indeed seems to work on the OpenWrt side and the verification – both of them, through the service_name and the direct link. Yet I still don't see an update on dynv6.
Any thoughts? I will try to contact the support on dynv6 if there is any apart from the dead forum.
I just put the address to my web browser and got a reply "address unchanged". I guess the indicator "last update" on dynv6 changes only when the address changes. I guess it is alright now.