Public Service Announcement: DuckDNS

Node Operators
1

There have been numerous posts/report of failing nodes, misconfigured QUIC, suspension particularly on EU & Saltlake…

99% of these issues are related to using a DDNS service and, in particular, DuckDNS. The DuckDNS service has been facing growing inconsistency and failures for several months now.

Do not use DuckDNS. If you are using DuckDNS change to another provider.

Lots of options out there and I’m sure people here will help. Some quick examples:

  • no-ip.com (free but you have to verify every 30 days)
  • dynu.com (also free)
  • cloudflare (truly free if you already have a custom domain)
  • many others…

Just get off DuckDNS.

Thanks.

(rant off)

2 Likes
2

It could also be because of this bug in ddclient 3.x get_ip returns random IP from HTTP headers · Issue #818 · ddclient/ddclient · GitHub

I use namecheap and got hit by that bug.

3

One could simply script an external ip update for config.yaml.
You can curl some external ip echo urls:

ifcfg.me
ifconfig.me/ip
ip-adresim.app
icanhazip.com
myexternalip.com/raw
myip.dnsomatic.com
and Amazon's ip echoer @ https://checkip.amazonaws.com/

or by reverse DNS lookup:

nslookup myip.opendns.com resolver1.opendns.com.

3 cents
Julio

4

It requires to restart the node (filewalker and so on).

5

mmm seems i just got hit with this… some of my nodes are getting suspended on saltlake and eu, but working fine on us and ap1..

guess i’ll need to graceful exit the node and restart it…

6

Graceful Exit is not the same as gracefully stopping the node. The latter entails using -t 300 in the stop command.

1 Like
7

Why? Suspension is not disqualification.

8

oh hey that is true!.. so i just switched my ddns provider… everything is back up now… mmm but i was suspended for more than 14days it seems… not sure if it can recover… i didn’t get a disqualification email, so i guess i should be fine

9

Setup remote monitoring for your node endpoint, for AllHealthy value. It’s free and takes 2 minutes.

10

The node should be 30 days online to fully recover the online score. Each downtime requires an additional 30 days to recover.
However, when the online score would be greater than 60%, your node would be unsuspended.