Namecheap Dynamic DNS cached ip 0.0.0.0 issue
-
@tribesstorm
As said, the DNS update seems to succeed. You can verify by an nsuplook.But pfSense checks the server respond, when using the Namecheap client and compares it with its hard-coded success-answer. If that doesn't match it throws an error for the update.
You can configure a custom client and leave the "Result Match" box blank, so the response is not verified, or even enter what Namecheap actually give back, when the update succeeded.What's your recommended alternative registrar that works well with pfsense?
But yeah, seems Namecheap changes its response quite often.
I'm using the SPDYN and freeDNS for years without such issues. -
@viragomann Thanks! It looks like creating a custom entry worked.
-
V viragomann referenced this topic on
-
V viragomann referenced this topic on
-
This could be a change by namecheap again but you can see in the logs posted that the errcount does indeed equal 0 so it seems like PFsense is not parsing it correctly. Any suggestions as to how we can fix it so we don't have to use a custom service without a reponse as that seems to just remove the response and not do any verification that the DNS is actually updated. I I can manually check but ideally, I would like pfsense to be able to check it so I can see visually on the dashboard that records are updated without having to manually check.
-
@samh said in Namecheap Dynamic DNS cached ip 0.0.0.0 issue:
you can see in the logs posted that the errcount does indeed equal 0 so it seems like PFsense is not parsing it correctly.
Yeah, as mentioned above here, updating the DNS will work anyway, but pfSense gets no confirmation from the server.
pfSense is expecting specific known response data, but the server sends something else. Hence it says "unknown response" and cannot confirm that the update succeed.
The expected response is hard-coded in pfSense. But hey, it's open source, so you can change it if you want.
-
@viragomann Thanks for the response. Unfortunately, not a skilled developer (I only dabble) so I took the path of least resistance and moved to another Dynamic DNS Provider.
-
Got the same issue here. Found the problem is the utf-16 vs utf-8 response Netgate expects. You can fix it but you have to edit /etc/inc/dyndns.class
Goto line 1712 and change $data to $data_tmp so the line is:
$data_tmp = substr($response, $header_size);Then add this line underneath it:
$data = str_replace("utf-16", "utf-8", $data_tmp);This will get you your green status and cahed ip.
-
-
@steveits - Which patch package is that as i'm running the 3100 netgate with 22.05 stable and it's up-to-date.. Ahh i see in the Redmine issue: the plus target is 23.01. That is still the dev version. I'm running the stable so when 23.01 becomes stable this won't be an issue anymore.
Thanks
-
@wazari System Patches is an add on package by Netgate that has fixes not in the release versions. The fixes eventually roll into the next version of pfSense.
-
@steveits - Yes saw it. Thanks..
So for now my 22.05 version works with the fix, thats fine -
@steveits Patch is not available in Patches for people running PFSense+ v22.05
-
@aheadalarmroom On 22.05 I have applied:
Namecheap DDNS on 22.05Ensure you have the latest Patches package. They add patches via a package update as opposed to an external list.