-
not a pfsense issue but is anyone else seeing issues with duckdns? It updates under Services/Dynamic DNSDynamic/ DNS Clients but don’t update under my account at https://www.duckdns.org/domains. After wasting enough time playing with it I opened a No-IP free account and it working and updating as it should.
Just wondering if it locked me out? I did a clean install of 2.7.2 on a second router and exchanged hardware a few times to make sure I’d duplicated my settings correctly. I’m thinking maybe the back and forth with the different IP’s put a stop to the updating. any thoughts?
-
any thoughts?
Yeah, one.
Every 'free' dydns has build in an 'abuse' detector : when you update the IP 'to often' they'll block further updates. This is to protect their systems.
Partial explication : most dyndns updates are done by scripts. If 'something' goes wrong, these script will start to update - fail - no problem, update again etc etc etc etc. This will take down the service for everybody. So, hence the protection, which is most often based on some sort of 'fail2ban' protection : of your WAN IP pops up to often ; ban for x time.Most often the 'not free dyndns' services are far more flexible (less error prone), and with an understandable reason : you pay for it.
Nice side effect : they make you think : "If I pay for it the service, will I have have better service ?" ( yeah, don't laugh now )Btw : very IMHO, these just my thoughts, as I discovered it when I was 'fed up' with the good old dyndns.org and decide to make my own dyndns, and give my friends and friends of friends access to my own 'dyndns'.
Then things went bad ..... and I learned the rules the hard way.The free no-ip forces you to take action every month with their web interface, where your have to click several times to find the button, "I want one more free month". So, free, indeed but they make you 'work' for it. (not sure if this is still the case, though)
-
@Gertjan thank you for the reply back, Guess that explains it, I've been using it since 11/2020 and this was the first time it tanked on me.
-
Mine is currently working (just checked the IP) and untouched for over 6 years. When I first set it up on pfSense.
-
I just discovered duckdns is working and likely had been the whole time, as a test I added a 2nd domain on the duckdns site which displays the current IP address.
What’s not working is the first and original sub domain which is locked on the prior IP. I guess that is the damage from too many updates in one day. I could live with that, I only have to change/ update three WireGuard client endpoints.
