DDClient updating record with incorrect public IP. DDClient updating record ...

Topic: DDClient updating record with incorrect public IP.

Post DDClient updating record with incorrect public IP.
by junkmail50114LH on 2020年5月26日

I have your DDclient running on my raspberry PI as per your instructions with the URL:

echo url="http://api.dynu.com/nic/update?hostname=lovellshall.dynu.net&password=PASSWORD" | curl -k -o ~/dynudns/dynu.log -K -

but the IP address that is updated does not match the public IP address of the device. Is there a mistake with my script?

Reply with quote | Report
Post Re: DDClient updating record with incorrect public IP.
by rahsharma on 2020年5月26日

junkmail50114LH wrote:I have your DDclient running on my raspberry PI as per your instructions with the URL:

echo url="http://api.dynu.com/nic/update?hostname=lovellshall.dynu.net&password=PASSWORD" | curl -k -o ~/dynudns/dynu.log -K -

but the IP address that is updated does not match the public IP address of the device. Is there a mistake with my script?
You can check what IP your device is using to get to the Dynu servers using the following link:

https://api.dynu.com/ipcheck.asp

It is possible that your device is using IPv6 to get to Dynu name servers which will result in the IPv6 address getting updated instead of the IPv4 address. If you can post your configuration here without the username, domain name or password, we could provide you better feedback.

Reply with quote | Report
Post Re: DDClient updating record with incorrect public IP.
by Quaxth on 2020年5月27日

I had a similar problem: IP shown was not accessible over the Internet and neither any even correctly forwarded Port! Also, any RDP or Remote Control wasn't working!
After having the ISP send a Service Engineer, they're needed to change in their Servers the IP from Net-IP to Public IP. Done that, everything was working well include RAdmin Remote Control and any open Port was available, as well as the commands Tracert and Ping also were working correctly!
I then remembered that those problems were starting after the ISP was changing the connection from Cable to Fibre with a change of the Modem Router about a week earlier! The IP shown in the Status page of the router was never changed, it was pingable but accessible! The IP is shown using tools like the API from DYNU, it was not the true public IP it just was the Net-IP. After that change by the ISP Service, it shows now the true Public IP in the Status Page of the Router and changes as the Dynamic IP changes every time.

Reply with quote | Report
2020年7月13日 19:41
Loading...