I'm in trouble in dyndns ..
May 24 12:21:52 php-fpm: /services_dyndns_edit.php: phpDynDNS (xxxxxx.dyndns.info): PAYLOAD: badauth May 24 12:21:52 php-fpm: /services_dyndns_edit.php: phpDynDNS (xxxxxxx.dyndns.info): (Unknown Response) ```![dyndns.jpg](/public/_imported_attachments_/1/dyndns.jpg) ![dyndns.jpg_thumb](/public/_imported_attachments_/1/dyndns.jpg_thumb)
A badauth would indicate a bad username or password, would it not?
User and password are correct
Yep, thats what I am thinking.
Did it ever work? Is this the first time you have used it?
Check your settings, make sure your hostname is correct, username and password are correct (not sure if case sensitive).
I don't know what you're using as a username, but just for information as I do not know if you know or not…. your username is not your email address, some have reported as using it and it fails. You login with your email address on the site, but use the username for DynDns clients. I have been using DynDNS for about 10 years or more....
Jailer last edited by
Had that happen with me once with dnsafriad and a reboot took care of it.
Did you fix your issue?
Dear all, sorry for hijacking issue, but i have same. Today i got new ip by modem reboot but now dyndns wont change cached IP.
I have this error.
Aug 26 20:19:23 php-fpm: /services_dyndns_edit.php: phpDynDNS (xxxxxxxxxx.dyndns.org): (Unknown Response) Aug 26 20:19:23 php-fpm: /services_dyndns_edit.php: phpDynDNS (xxxxxxxxxx.dyndns.org): PAYLOAD: badauth
It was working like this for ages, but suddenly stop. What could be issue?
built on Sat Jul 25 19:57:37 CDT 2015
many thnx in advance :)
Some Dynamic DNS providers cant be updated when your fw IP address is the same as whats already showing with the Dynamic DNS provider.
Getting a new IP from your ISP can usually help but it depends on when your ISP allocating you a new IP address, alternatively log into your Dynamic DNS provider and put a wrong ip address in, then wait for pfsense to update and it should work.
I solve this one,… seems that we cannot use regular login and pass acc. We need to use login as usual, and unique key from dyn.com which will authenticate it properly.
So yeah, its fixed but its really strange.