I have tried comma separating my 2 domains and it does not seem to work.  Do you support this?

Works for me with "coppit,coppit2". You'll need to give more info. Make sure you didn't insert a space before or after your comma-separated list.

Sometimes my docker container host will lose internet connection. This will cause the curl command to fail and duck.sh/container to quit. Would it be possible to swallow the error and just keep running?

Sometimes my docker container host will lose internet connection. This will cause the curl command to fail and duck.sh/container to quit. Would it be possible to swallow the error and just keep running?

 

Initially I was doing this..,

 

DOMAINS=domain1,domain2TOKEN=xxxxxxxxxxxxxxx

 

After reading your reply I tried quotes

DOMAINS="domain1,domain2"TOKEN=xxxxxxxxxxxxxxx

 

this seems to work fine.  One domain works without quotes.  Anyway, thanks for your help

 

Thanks. I suspected something like that. I'll add quotes to the default config to help people from the start.

Hi.

 

Are there any ports that I need to open for this that might have changed? It worked great but after an update I'm posting "KO" in the log. the token and domain seem fine. I tried with and w/o quotes.

 

Thanks, Kenny.

Are there any ports that I need to open for this that might have changed? It worked great but after an update I'm posting "KO" in the log. the token and domain seem fine. I tried with and w/o quotes.

 

No, there aren't any ports to open. Here's the default config:

 

DOMAINS='yourdomain'
TOKEN='yourtoken'

 

It's pretty simple.

 

Try logging into your unraid server and running this:

 

curl -S -s "https://www.duckdns.org/update?domains=yourdomain&token=yourtoken"

 

replacing yourdomain and yourtoken as appropriate. If that works but the container doesn't, let me know.

I've updated the code to be more tolerant of problems connecting to www.duckdns.org. I found that my container had stopped due to a temporary network glitch.

Thanks Coppit. This is an awesome docker and DuckDNS is an awesome service.

 

Given you can use your own domain it's great for $0

I've added an "INTERVAL" configuration value.

 

If you are upgrading from a previous version, you will need to add an interval to your config file. Example:

 

INTERVAL='30m'

 

The new default interval for new config files is 30m. The minimum allowed is 5m.

I'm not sure what I'm doing wrong. It keeps stopping on me. Here is my config file.

 

DOMAINS='<myname>.duckdns.org'TOKEN='5xxxxx7'INTERVAL='30m'

 

/config points to /mnt/user/appdata/duckdns/

 

Thats where my duck.conf is.

 

What other information can I provide?

 

EDIT: I did the curl -S -s "my url and key" and it says "KO" in front of root@Tower now

 

Take the duckdns part out.  It should just be MYNAME...at least thats how it works for me.

Awesome thanks! I knew it was something stupid.

Wanted to say this still works like a champ, very happy it's up and going, no issues.

It's so simple, it's hard to imagine how it could stop working, as long as the server side of their service keeps going.

 

I noticed this at work... I need a pithy way to capture it... Something like "Mo' code, Mo' problems". The idea is that every bit of complicated code has cost that is higher than it seems. So if you find yourself writing complicated code, you're going to regret it later.

 

KISS principle, I guess.

New update is out.

 

I moved from the phusion (Ubuntu-based) base image to Alpine. The image is 5x smaller.

 

Also, you can now specify all the settings using only environment variables. In this case you don't need the config file. Env vars take precedence over the config file values.

Having an issue with the docker communicating to DuckDNS. Vars are specified in the settings but seeing the below error:

 

./run: line 3: /etc/envvars.merged: No such file or directory
Will detect ipv4 automatically
[May 15 04:35:26] DuckDNS reported an error. Check your settings. Result was "KO"