I’m seeing this same issue:
Read the whole topic you are responding to. It was literally discussed a day ago right in this thread.
This is your problem:
2 Likes
Fair point. I thought I had, but clearly was lacking sufficient coffee when doing so. Looks like I was impacted by using duckdns for my node IP/DDNS. Thanks for pointing this out.
Switched to dynu and it’s cleared up. Guess I’ll need to finally spring for a paid DDNS service. 
2 Likes
I’m confused. I could not have known you used duckdns….I thought I replied to Joss? I’m lacking coffee too…
Please don’t. Ddns is often offered for free as a value add to services you likely are already using. See that same comment above for recommendations. Your domain registrar would be the first entity to check.
1 Like
I am sticking with “free” for now, but moved my node DDNS to DYNU. I got into the DuckDNS “google group” and it looks like the service–which I think has been solid for years–has been having some issues recently.
It has a chance of working, as they have revenue streams from paid services and free ddns is just a good marketing, a loss leader. Duckdns - does not. It was started by two naive dudes that decided that modern offerings are either too expensive or unreliable and they of course could do better for free (or at least that’s what they wanted everyone to think). Then reality struck.
I don’t know why would anyone use it. Seriously. No idea. It seriously has no future. Once they get fed up supporting it for free and paying amazon bills it will shut down.
Remember, any decent domain provider offers api to edit dns. That’s it. That’s your DDNS right there. Costs nothing.
I’ve read the thread and all the comments. But my English isn’t very good. I meant to say that my DuckDNS has the correct IP address at all times. In fact, it’s been the same for years and it’s correct. What doesn’t make sense is that some servers find the node and others don’t, even though the node hasn’t been down at any point, and the IP address is the correct one.
I’m going to read the thread again and continue investigating.
I believe, after reading the DuckDNS “support” group, that the service has been having intermittent issues over the last several weeks/months. There is no further information. I would suggest you move to a free DDNS service, from a provider that–as @arrogantrabbit pointed out–has other paid services that support this “free” service. I moved over to DYNU.com.
I used to actually use no-ip.com a while ago and guess I should have stuck with it.
1 Like
I have a domain on 1and1, does anyone know if they provide this service?
That could explain everything. And the fact that the subdomain resolution isn’t being replicated correctly in other DNS servers on different sites.
1 Like
I’ve move the node from duckdns the Noip. Now QUIC is not misconfigured anymore, BUT I’ve lost EU satelite. Don’t know how and why that’s happaned, since the node is in EU.
The Others look fine.
I’ve created a subdomain (storj01.domainname.es) and pointed it to my public IP address. I thought I saw that it could be updated somehow, but for now, since my IP address doesn’t usually change, I’ve done so while I finish fixing it so my node isn’t penalized further.
I deleted the Docker container and regenerated it with the newly updated domain configuration.
Everything seems to be OK for now, pending a fix for automatic updates. Especially since I use another backup IP in case the main line goes down.
It’s correct when you check it, but it may be incorrect when satellite checks it: from different location, talking to a different instance of duckdns, that is broken, or did not replicate correct data, for example.
What is “1and1”? When I google it, it sends me to ionos.com. Which has Set up Dynamic DNS with IONOS - IONOS Help
Check out GitHub - troglobit/inadyn: In-a-Dyn is a dynamic DNS client with multiple SSL/TLS library support
2 Likes
Fellow DuckDNS user here, just chiming in to confirm I’m having the exact same problem on my two nodes. Still showing as misconfigured as of March 20, and it’s specifically affecting the EU and Saltlake satellites for mine, too. The funny thing is I swapped from No-IP on an old node to DuckDNS since I got tired of those monthly renewal emails, but I guess I traded one hassle for another.
Any idea why a DDNS provider issue like this would impact those two and not the US or AP ones?
1 Like
Perhaps replication between their instances failed. US and AP may be running in the same Amazon region that your updater connected to to update the record, and the other two in another, haven’t updated or otherwise returning garbage.
DNS is too important to delegate it to some free best-effort type of service.
1 Like
Maybe this is related?
Unlikely — this would result in wrong address being sent to the DDNS provider — node would not work at all. In this case it’s the opposite: correct address is sent, but for some users (satellites in this case) DDNS provider returns bad data.
But this bug is hilarious who does that… and ddclient exists since forever.
1 Like