When one DynDNS entry is force-updated the others get N/A for Cached IP
-
This has been going on for a long time. I just upgraded to CE 2.9.0 but it was the same 2-3 versions back. The 2.9.0 has some issues with updating DynDNS when on PPPoE but that's another story and I will post about it when I gather more information.
The relevant problem is when I go to DynDNS entry and do "Save and Force Update" this entry is updated but all others show N/A for cached IP. I had to force-update one entry after a reboot. In 2.9.0, after every reboot some entries are not updated. And every reboot changes my IP, courtesy of my ISP. So I did force updates for those that were not updated.
Now it seems easier to reboot to recover all those cached IPs, but after a reboot, some entries may not be updated, and it goes into a loop.
Someone, please look into this. This issue has been there for years.
One note. When I do "Save and Force Update" it takes a long time to refresh the page, maybe a couple of minutes. Longer than it should. And it does the update twice - Pushover sends me two messages within a few seconds notifying me about the IP update.
-
So, two days later I had the same situation with DynDNS except instead of "N/A 18:14:06" I had 0.0.0.0 in red in the table. I decided to reboot, hoping it would update the records. But no, after the reboot pfSense didn't even try to update DynDNS. Minutes (I waited) after the reboot I had this:
Now I am manually force-updating each entry, and I am getting Pushover notifications TWICE for each entry. DynDNS is very broken. Can anyone look at it, please?
-
Can you list the dot cache files in the /conf/ folder ?
These contain an IPv4, the | and then a time stamp.
You found inconsistencies ?About the DDNS provider : the DDNS update event kicks in when the interface, WAN typically, changes. In your case, that's not 'one' update, but many.
Guess what DDNS provider does not like fast frequent IP updates (I'll help you : none of them). So, it might be possible that they flag this massif update as 'abusive' as all the updates update to the same IPv4.
The user applies the standard conclusion : "(dyn)DNS is broken" which is often true, up untill the moment the suer start to read the "usage condition" ... and now he knows who broke what and why. ^^
I'm not implying that this is the your issue right now. To be sure, I want to see the logs, see what happens on the porkbun side, etc. I'm just mentioning 'a situation' as it's know for decades now.
I'v hosted a pretty big DynDNS service (3000 host max) myself and several broken DynDNS clients can take your service down, so, severe rate limiting wasn't an option anymore. This also explains why there are no really good free DynDNS anymore : it's to much of a hassle to keep them free.So, if possible, show more details, so we, the forum users, and those who (think that they) know something about DynDNS can start imagining what goes wrong in your case.
-
P pfpv referenced this topic
-
-
Is it, or it was ?
I saw the pppoe package (kernel ?) was updated yesterday, or the day before.
You have to console (ssh), option 8, and "pkg upgrade" it. -
@Gertjan
I was going to ask for more info but found the discussion:
https://forum.netgate.com/topic/198696/if_pppoe-ping-works-but-dns-doesn-t/53However, that fix has nothing to do with this issue. Actually, the bug I mentioned has nothing to do with this issue. I posted too soon. This issue existed before 2.9.0. That bug showed up only in 2.9.0.
Privacy Policy · Cookie Policy