Duckdns keeps changing the public IP I entered

Configuration
1

hi there,
i have a really strange issue here … have a HA instance in my van which is connected over a peplink fusionhub hosted on a AWS ec2 instance … this has a public IP address in the range of 52.x.x.x and is static … when I enter this IP in duckdns to enable SSL access => duckdns changes my given IP address to a complete different one in range 212.x.x.x
so weird !!! cannot reproduced what is happening … must have something with fact that this virtual appliance runs on AWS …
trying now with no-ip ddns and lets encrypt add-on
but still … any hints on that duckdns phenomenon
cheerz from vienna

2

Are you using the DuckDNS add-on?
In the DuckDNS.org website, you don’t enter the public IP, DuckDNS does.

3

now I am confused … I used already duckdns.org to create a domain and to connect it with my home public IP address … and I did enter this IP in the according duck DNA.org form …
and want to do the same for my van HA instance …
hmmm :thinking:

Screenshot_20230816-204858
Screenshot_20230816-2048581080×2340 187 KB

4

If you are using the Add-On then go into the Add-On, and check the log.

What IP address is shown there?

Do you have separate URLs in DuckDNS for your home and for your van?

5

hi,
yes i have different URLs and different IPs for home and van

  • the IP for home i entered month ago in duckdnsorg and is stable
  • the IP for the van is updated automatically after some minutes by duckdnsorg

log says

INFO: Using main config file /data/workdir/config

  • Account already registered!
    [07:35:25] WARNING: KO
    [07:35:28] INFO: Renew certificate for domains: cactushamburg.duckdns.org and aliases:

INFO: Using main config file /data/workdir/config

Processing cactushamburg.duckdns.org

  • Checking domain name(s) of existing cert… unchanged.
  • Checking expire date of existing cert…
  • Valid till Nov 14 09:14:40 2023 GMT (Longer than 30 days). Skipping renew!