Namecheap with DynDNS receives "unknown response" after upgrade to 21.7

[franco]

It might be an improved validation with some recent PHP 7 update so that the error was there quite a while, but in any case our side is not a fix indeed.


Cheers,
Franco

[iBROX]

Thank you Franco, applied the patch and the issue has been resolved.

Great work!

[franco]

Not resolved, just diagnosed and temporarily fixed. As soon as they fix their file to emit UTF-16 characters instead of UTF-8 it will break again on our end...


Cheers,
Franco

[katamadone [CH]]

This means the issue is on namecheap's end, as I understand it.

I already brought this up to a namecheap rep and they said they're investigating.
https://www.reddit.com/r/NameCheap/comments/qz1mjf/namecheap_dynamic_dns_returning_utf16_encoded/hljqzja

Same here, did you hear already something from namecheap?
Do you have a ticket number? If needed / wanted I'd submit one or two more at namecheap (company and private account).

[eschmacher]

Same here, did you hear already something from namecheap?
Do you have a ticket number? If needed / wanted I'd submit one or two more at namecheap (company and private account).

I just asked the rep on reddit and they said they didn't open a ticket. If you have the ability, that would be great. I fear without one, this will get sidelined from them.

[lcasale]

I just opened a ticket with them. Will post back when I get updates

[ezhik]

Any updates?

[ezhik]

so the plugin update, seems to be working now! Thank you all!

[franco]

Sure, workaround is applied now in the release, but it could break again so let me know if that happens. :)


Cheers,
Franco

[katamadone [CH]]

I just opened a ticket with them. Will post back when I get updates

Did you hear something? Or do you have a ticket number? So I would file one, too - with reference to your ticket.

[phaze75]

I am not sure if this is the correct thread, but I post it anyway.

I have also issues with the dyndns service. I use freedns. Since the last update of the package to version1.27_1 the update of a change IP doesn't work anymore. Please find the log entries below:

Code Select Expand

2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): (Unknown Response)
2021-12-16T01:11:02 opnsense[79456]
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): PAYLOAD: Error 404 : Page not found
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): Current Service: freedns
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): _checkStatus() starting.
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org via freeDNS): _update() starting.
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): running dyndns_failover_interface for wan. found igb0
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): 80.108.241.82 extracted
2021-12-16T01:11:00 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS: updatedns() starting


The service status shows the value "n/a" in the field "Cached IP". This is awkward as the service seems to extract the correct IP according to the logfile...

Could this also be connected to the issues with the last version 1.27_1?

[franco]

Really not a great place to post FreeDNS issues in well-known Namecheap topic.


Cheers,
Franco

[phaze75]

Really not a great place to post FreeDNS issues in well-known Namecheap topic.

Well, I thought that this might be a general issue of the dyndns package independent of the DNS provider. Should I better create a new topic?

[marjohn56]

Yes, otherwise it makes it harder to keep track of things.

[phaze75]

Yes, otherwise it makes it harder to keep track of things.

Done. Please delete all my posts in this thread including this one. Sorry for the inconvenience caused!