Dynamic DNS Cached IP Won't Update
-
Been digging on this for over an hour now and can't seem to figure it out.
I have a new Netgate 6100 and love it, manually copied all my settings from my previous unit (always do this instead of restoring from backup, gives me a good chance to re-review all my settings), and so far 99% of things are working perfectly.
However, I can't get Dynamic DNS to work. Within the Dynamic DNS server it's showing my cached IP as 0.0.0.0 and won't update no matter what I do, reboot the entire unit, save, save and force update, etc...
I've verified the correct interface is selected, and in the dashboard and Status > Interfaces section the right IP is shown for this WAN interface.
I've also verified my Cloudflare API key is working fine, and checkip.dyndns.org loads just fine with the right IP from multiple VLANs.
The only thing that is MAYBE hinting to me is that I did a bit of an odd thing with WAN and added a new one on the 2.5GbE ports since my WAN is capable of over 1 gigabit (and negotiates at 2.5). I have the right interface selected in the DynDNS settings though so I doubt that is the issue, it's just the only thing I can think of that is slightly different about my implementation than other ones I have in the wild.
I'm definitely not inexperienced with PFSense and firewalling in general, and I have a lot of units with Dynamic DNS in play in the wild and none of them have ever had a single issue. So really no idea what is going on here.
-
@planedrop A small update to this, no matter what interface I use in Dynamic DNS settings it shows the cached IP as 0.0.0.0, so seems it's just not grabbing the IP of the interfaces at all, period...
-
Another update here, manually editing the Dynamic DNS file seems to have worked, no idea why it wasn't updating before though and I'm guessing it won't auto update like it should.
I updated the critical one that I need to work right now, will wait for the non critical entry I have to see if it auto updates after 24hrs (I have manually adjusted cron to check every 5 minutes but that doesn't seem to be helping).
I'm also getting some dynamic DNS errors in my logs, including a general Unknown error and a "wan IP could not be determined..." one.
-
Take that back about it working, while it does verify the IP is correct with Cloudflare, it doesn't actually push any updates no matter how many times I try to force the update.
-
So things are getting even weirder.
I deleted all my DynDNS entries, then re-added one of them, it showed green because the IP matched but was clearly not actually pushing the update.
I added the second one, after adding the second one the first one now has the cached IP updated to "N/A" even though it wasn't touched.
Logs are continually displaying the below:
Jan 22 13:42:50 php-fpm 354 /services_dyndns_edit.php: phpDynDNS (*********): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. Jan 22 13:42:35 php-fpm 354 /services_dyndns.php: phpDynDNS (****): UNKNOWN ERROR - Jan 22 13:42:35 php-fpm 354 /services_dyndns.php: phpDynDNS (*****): PAYLOAD: Jan 22 13:35:07 php 22378 rc.dyndns.update: Dynamic Dns (******): Current WAN IP could not be determined, skipping update process. -
OK big update to this now, I seemingly figured out the issue but no idea why this was happening and think I maybe should fill out a proper bug report about it?
So it was related to the WAN interface being changed from the default like I had suspected.
Long story short, I had added an interface for WAN which I'm using as primary and had the default WAN interface that can't be removed assigned to a random VLAN and not in use. The one thing I had forgotten to do is to disable the default WAN interface.
However, I have NO idea why this would make it so the Dynamic DNS system would not pull the public IP for the other WAN interface which was the one that was selected in the DynDNS settings area (which was grabbing N/A or 0.0.0.0). But for some reason after actually disabling the default WAN interface it came back up perfectly normal and pushed an updated to Cloudflare.
One final thing though, and I recall this may have happened on my previous installation, but when doing a Save & Force Update the page hangs and never finishes loading (waited over 5 minutes), but I can witness the logs showing a successful push to Cloudflare and see the IP update on Cloudflare's side, so I can just go back to the home page and back to the Dynamic DNS section and everything is green.
-
Hmm, that does seem odd. Was it in a gateway group? Some sort of conflict wit the new WAN?
I assume other traffic was using the new WAN as expected?
Steve
-
@stephenw10 It wasn't in a gateway group of any sort, seems like some conflict was happening but not sure why.
All other traffic was using the proper WAN that I had configured and there was only one actual gateway in the routing settings.
I've since removed that second WAN interface that I created and am using the default created one, everything is working exactly as it should now. (was coming from a 2 WAN setup but don't need both anymore, hence this sort of odd initial configuration). I can confirm that disabling that default created WAN interface fixed all the issues I was seeing with DynDNS though, pushed updates to Cloudflare 3 or 4 times to be sure it was working consistently.
-
Tried posting my issue, but Akismet sees it as spam for some reason.
I am having a very similar, albeit a bit different, issue with Dynamic DNS.
