topsbr
December 8, 2019, 8:46pm
1
Hi all...
I'm having problems with ddns client that I can't solve ...
Resume on Status page:
Check of my IP on www.meuip.com :
The IP addresses are different!
Configs of ddns service:
config ddns 'global'
option ddns_dateformat '%F %R'
option ddns_loglines '250'
option upd_privateip '0'
config service 'myddns_ipv4'
option interface 'wan'
option ip_source 'network'
option ip_network 'wan'
option service_name 'no-ip.com'
option enabled '1'
option lookup_host 'tl-wdr4300.servebeer.com'
option domain 'tl-wdr4300.servebeer.com'
option username 'rodrigo.roberti@gmail.com'
option password 'password'
option use_syslog '4'
option check_interval '15'
option force_interval '24'
Log of ddns service:
173921 note : PID '10825' terminated by 'SIGTERM' at 2019-12-08 17:39
173928 : ************ ************** ************** **************
173928 note : PID '25270' started at 2019-12-08 17:39
173929 : ddns version : 2.7.8-1
173929 : uci configuration:
ddns.myddns_ipv4.check_interval='15'
ddns.myddns_ipv4.domain='tl-wdr4300.servebeer.com'
ddns.myddns_ipv4.enabled='1'
ddns.myddns_ipv4.force_interval='24'
ddns.myddns_ipv4.interface='wan'
ddns.myddns_ipv4.ip_network='wan'
ddns.myddns_ipv4.ip_source='network'
ddns.myddns_ipv4.lookup_host='tl-wdr4300.servebeer.com'
ddns.myddns_ipv4.password='***PW***'
ddns.myddns_ipv4.service_name='no-ip.com'
ddns.myddns_ipv4.use_syslog='4'
ddns.myddns_ipv4.username='rodrigo.roberti@gmail.com'
ddns.myddns_ipv4=service
173933 : verbose mode : 0 - run normal, NO console output
173933 : check interval: 900 seconds
173934 : force interval: 86400 seconds
173934 : retry interval: 60 seconds
173935 : retry counter : 0 times
173935 : No old process
173935 : last update: 2019-12-08 17:27
173935 : Detect registered/public IP
173936 : #> /usr/bin/nslookup tl-wdr4300.servebeer.com >/var/run/ddns/myddns_ipv4.dat 2>/var/run/ddns/myddns_ipv4.err
173937 : Registered IP '177.76.142.235' detected
173937 info : Starting main loop at 2019-12-08 17:39
173937 : Detect local IP on 'network'
173938 : Local IP '189.110.253.195' detected on network 'wan'
173938 : Update needed - L: '189.110.253.195' <> R: '177.76.142.235'
173939 : parsing script '/usr/lib/ddns/update_no-ip_com.sh'
173940 : sending dummy IP to 'no-ip.com'
173940 : #> /bin/uclient-fetch -q -O /var/run/ddns/myddns_ipv4.dat -Y off 'http://rodrigo.roberti%40gmail.com:password@dynupdate.no-ip.com/nic/update?hostname=tl-wdr4300.servebeer.com&myip=127.0.0.1' 2>/var/run/ddns/myddns_ipv4.err
173943 ERROR : uclient-fetch Error: '8'
173943 :
173943 WARN : Transfer failed - retry 1/0 in 60 seconds
Status of Service on ddns page:
My interfaces:
It's very weird...
Note: My ISP modem has already been rebooted, it operates in brigde mode and always operated this way ...
Looking at the no-ip.com dashboard, I realize that the system received the correct IP ...
But when trying to connect remotely to the router, I just can't...
Thank you all!
What is the contents of file /var/run/ddns/myddns_ipv4.err?
topsbr
December 8, 2019, 9:51pm
3
Nothing in this file @eduperez
root@poseidon:~# cat /var/run/ddns/myddns_ipv4.err
root@poseidon:~#
tmomas
December 8, 2019, 11:43pm
4
Have you installed / uninstalled any packages a few days ago?
topsbr
December 9, 2019, 1:05pm
5
Hello @tmomas
I haven't installed / uninstalled anything from Open since the problem started, except ddns's own packages and configuration files.
Thanks !
On one hand, I would try to run "uclient-fetch" by hand, using the same parameters as the DDNS scripts but without the "-q" parameter (or perhaps there is an option at "/etc/config/ddns" to make the output more verbose).
On the other hand, the "myip=127.0.0.1" parameter in that call is a bit suspicious... but the logs say "sending dummy IP to 'no-ip.com'", so perhaps this is the normal behaviour (a look at "/usr/lib/ddns/update_no-ip_com.sh" could probably help here).
tmomas
December 9, 2019, 8:24pm
7
topsbr
December 9, 2019, 8:48pm
8
I will try @tmomas ...
But i decide that i will update the version of openwrt to 18.06.5, maybe tomorrow...
user@machine:~$ nslookup tl-wdr4300.serverbeer.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: tl-wdr4300.servebeer.com
Address: 177.76.142.235
Most importantly, did your DDNS account expire and you failed to follow the renew email?
This happens if account lapses.
topsbr
December 9, 2019, 10:23pm
10
It didn't work either ...
topsbr
December 9, 2019, 10:29pm
11
=> I can't open http://177.76.142.235:8081/ - no hostname involved
=> I can't reach http://189.110.253.195:8081/ either
=> The error page you posted appears to be from a local Squid cache server named br-cn-prx-01.brastorage.local
=> Perhaps the server at port 8081 is down?
=> The account is working perfectly on no-ip ...
topsbr
December 9, 2019, 10:51pm
12
Unfortunately it persists ..
Then contact them, as your IP has not changed in the global DNS.
topsbr
December 13, 2019, 2:38pm
14
Hello everyone ... I came back after updating my router to version 18.06.5 and reconfiguring my provider's modem to perform new tests on no-ip ...
What is strange to me, according to the prints and log below, is that the no-ip script that runs on OpenWRT is working correctly, but I don't know why it doesn't send the update to the no-ip site and with that, I can't access the router remotely as it was possible before.
Strangest of all, it used to work correctly, and because of that, I think now I can only open a support ticket with no-ip, and even if I delete and create my notes again, it works until that my IP is changed again ...
Here are some additional prints ...
IP of my WAN: (eth0.2)
Also note that there is probably a bug in Luci, which does not update the ip address shown in the log ...
Log of DDNS service:
Router access from my work network:
Configuration of DDNS service:
config ddns 'global'
option ddns_dateformat '%F %R'
option ddns_loglines '250'
option upd_privateip '0'
config service 'myddns_ipv4'
option ip_source 'network'
option service_name 'no-ip.com'
option enabled '1'
option domain 'tl-wdr4300.servebeer.com'
option username 'rodrigo.roberti@gmail.com'
option password 'my_password'
option lookup_host 'tl-wdr4300.servebeer.com'
option use_syslog '4'
option check_interval '15'
option force_interval '24'
option interface 'wan6'
option ip_network 'wan6'
I'm currently getting NXDOMAIN when looking up your FQDN.
user@machine:~$ nslookup tl-wdr4300.servebeer.com
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find tl-wdr4300.servebeer.com: NXDOMAIN
Have you edited the TTL to a value other than 300 seconds?
topsbr
December 13, 2019, 3:08pm
16
Hello @lleachii ...
I believe and I'm almost 100% sure I didn't edit it, but if you can tell me the way, I can check and return the current value here ...
Testing from network of my work:
C:\Users\rodrigo.roberti>nslookup tl-wdr4300.servebeer.com
Servidor: br-cn-dc-02.brastorage.local
Address: 10.1.10.21
Não é resposta autoritativa:
Nome: tl-wdr4300.servebeer.com
Address: 189.110.252.129
10.1.20.21 is a DNS Server f my work.
Thanks!
You should know that information; but luckily I also have NO-IP.
It seems you cannot make such a change, but can you screenshot the "Last Update " page?
And the record it gave you is incorrect - we know this.
topsbr
December 13, 2019, 5:45pm
18
Last update, when I delete the 2 appointments and I create again...
1 Like
OK:
Doing a Whois for SERVEBEER.COM:
Name Server: NF1.NO-IP.COM
Name Server: NF2.NO-IP.COM
Name Server: NF3.NO-IP.COM
Name Server: NF4.NO-IP.COM
Testing your Authoritative Servers:
user@machine:~$ nslookup NF1.NO-IP.COM
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: NF1.NO-IP.COM
Address: 194.62.182.53
Name: NF1.NO-IP.COM
Address: 2a07:dc00:1820::53
user@machine:~$ nslookup tl-wdr4300.servebeer.com 194.62.182.53
Server: 194.62.182.53
Address: 194.62.182.53#53
Name: tl-wdr4300.servebeer.com
Address: 189.110.252.129
user@machine:~$ nslookup NF2.NO-IP.COM
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: NF2.NO-IP.COM
Address: 45.54.64.53
Name: NF2.NO-IP.COM
Address: 2607:f740:e626::53
user@machine:~$ nslookup tl-wdr4300.servebeer.com 45.54.64.53
Server: 45.54.64.53
Address: 45.54.64.53#53
Name: tl-wdr4300.servebeer.com
Address: 189.110.252.129
user@machine:~$ nslookup NF3.NO-IP.COM
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: NF3.NO-IP.COM
Address: 204.16.253.53
Name: NF3.NO-IP.COM
Address: 2620:0:2e61::53
user@machine:~$ nslookup tl-wdr4300.servebeer.com 204.16.253.53
Server: 204.16.253.53
Address: 204.16.253.53#53
Name: tl-wdr4300.servebeer.com
Address: 189.110.252.129
user@machine:~$ nslookup NF4.NO-IP.COM
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: NF4.NO-IP.COM
Address: 194.62.183.53
Name: NF4.NO-IP.COM
Address: 2a07:dc00:1830::53
user@machine:~$ nslookup tl-wdr4300.servebeer.com 194.62.183.53
Server: 194.62.183.53
Address: 194.62.183.53#53
Name: tl-wdr4300.servebeer.com
Address: 189.110.252.129
You need to ask NO-IP what the problem is.
In your last config:
config service 'myddns_ipv4'
The value should be 'wan', how was it modified?
