Duckdns

[Syreeta Malick]

in the wireguard interface the ip address "endpoint" every three days changes numbering causing congestion of the network. To avoid all this I create a DNs on duckdns but unfortunately this is not accepted because in the interface it is possible to insert only numbers and not letters.



duckdns

Download File https://t.co/5RLeDDmVUg






Does this mean that I will ALWAYS have to manually update the changing IP address? I saw from the duckdns website that the IP address does not change automatically, at this point what am I doing wrong because this IP is not transmitted to the DNS?


does anyone know what the settings should be for duckdns in the trucharts app catalog? i dont see any info on the truecharts docs, youtube videos, or just general google results. i am trying to do a duckdns for dynamic ip and then attach some letsencrypt certs to it.


If /usr/bin/caddy.custom does has duckdns as expected, then it should be working. Did you do the rest of the update-alternatives commands to make sure that version of the binary is active? Make sure to restart your systemd service after doing that so it loads the correct binary.


Hi Siquel,

This seems to be cropping up a lot lately.

Firstly it seems to me at least that your setup is a bit more extensive than it needs to be

Some of them are in conflict, e.g. You are setting an http component that points to your duckdns but later state that hassio be routed through home (127.0.0.1 etc.)

You also seem to be doing a lot with Port 80, I do nothing with port 80 and can access on local lan :8123 AND wan remotely (inside and outside my lan) on (note: no port specified as https defaults to 443)


I think we agree that Netgear is not likely to add more DDNS providers. I have not done extensive research, so I have no idea that should they decide to add more providers, duckdns.org would be one they would pick.


This is the command I used, and it does successfully generate me a certificate, which is confusing (because of my SSL issues).

Getting it setup had involved doing the duckdns method of adding a TXT record, which is through a custom web address. I also changed a TXT record on my other domain and successfully registered a certificate that way, but its not setup in my Pi to accept that domain.

Even without a SSL certificate, shouldnt I still be able to access my NextcloudPi server through the android app, but just without the extra security?






The DuckDNS integration allows you to keep your DuckDNS subdomain always in sync with your public IP address. DuckDNS is a free service that allows you to bind your own favorite subdomain under duckdns.org to the public IP address in use from your router, even though such address is dynamically allocated by your internet service provider and therefore changes over time.


Be patient. Dynamic DNS support will update public records, but it take a bit of time to propagate to the DNS you're actually using. It took about 10 minutes before I was able to ping my public IP. Pinging my not work for you if you're dropping it, it all depending on what you're doing. You can also nslookup .duckdns.org. Once it comes back with your public IP you know it's working.


Not sure if this is the right place to post this, however my IP changed the other day but I had to manually update it on duckdns.org, when I check the logs I get the following message repeated at 5 min intervals:


Thought I should have a go at some fault finding to get this problem sorted.

1 Checked that all the registered data with DuckDNS had been transferred to the Rockon.

Great first mistake, comma separated domain names separated with a period

Corrected that one.

2. Opened CLI in windows and pinged the duckdns domain name, all good there (3ms response).

3. Tried to access the ip address both internal and external, reply being:

My-IP unexpectedly closed the connection.

As the router has just been changed to a virgin Hub 4 due to Hub 3 failure, the next stage is to investigate the hub 4 settings.

Will let you know.


Having done all that I tried to connect with duckdns.org, as expected, still being refused, then with a flash of something to the brain, the public ip was tried with the :8086 port for Jellyfin and hey presto we had lift off.


It is clear that caddy needs to my-vw.duckdns.org domain in the HTTPS call in order to work.

But if I use dig to query the duckdns domain I am getting an empty IP address.

In Linux and Windows I can quickly solve this issue putting a static DNS mapping in the /etc/hosts but what about Android devices?

What solution do you recommend?


In the duckdns.sh script curl -k is used to connect to the duckdns server. The -k option is insecure because it makes curl skip the TLS certificate validation. A rogue site could steal the user's token and hijack their DNS entries, or learn which DNS names they have registered.


I can access Duplicati UI from HASS local IP, it works fine. I aware that there is a setting allow hostname here, but I dont know what should I input (mysubdomain.duckdns.org or mysubdomain only or duckdns.org or something else?..)

image1369730 102 KB


I entered a subdomain from DuckDNS in the local DNS records. My subdomain is Great-Wall.DuckDns.org. I can enter this domain in the url of my browser in the Pi-hole host and access the web interface. However, no other devices in my network can't. Strangely, I was able to access great-wall.duckdns.org once from a client PC but that was it.


May I double confirm more details about the DDNS not sending updates issue as follow?

1. Do you mean the public WAN IP is updated but the duckdns domain name resolves to a WAN IP that is still not updated (unchanged)?


2. How did you find this issue?

For example, you try to trigger the WAN IP change manually and then find the DDNS domain name resolves to a WAN IP that is still not updated.

Or you found there are no DDNS update logs on the controller so you thought the duckdns was not updated.


3. Could you please confirm if the IP shown in your duckdns server is the same as the current WAN IP?

You may try resolving the domain name on the PC with the nslookup command to see if the IP returned is correct.

Here is the link (point1 and 4) for your reference.


DuckDNS is a free dynamic DNS service. This service lets you pick a host name (i.e. "konnected.duckdns.org") that will always point back to your home internet connection even if your IP address changes from time to time. The DuckDNS add-on sets this up and automatically generates secure certificates for you via LetsEncrypt.


What finally worked was using Firefox, going to www.duckdns.org, opening the SSL certificate properties and exporting the root certificate and each of the intermediate certificates down the chain in order (I numbered the three of them for simplicity.) I then cleared out other test certificates, imported them in order one by one setting the very top one as a Trusted root CA - but not setting any of the intermediates as trusted root CAs and I did not import the DuckDNS certificate itself. I then created a new Certificate Profile and added each of the certificates to the profile in order, set the Certificate Profile that I created in the dynamic DNS profile and saved it.


For reference, the Advanced -> DDNS -> Hostname entry was set as the DDNS hostname *without* the .duckdns.org appended. API Host at www.duckdns.org, Base URI at /update, Secret Token pasted in with no spaces or other characters (generally the default DuckDNS v1 settings with my own private key.

f448fe82f3