Added by → luckman212 over 10 years ago. Updated about 10 years ago.
0%
Description
Namecheap DDNS allows '*' (wildcard), but the page does not accept this value.
Files
@ is already fixed -- see #6122
Try the fix on the ticket, if it works, this can be closed, if it still doesn't work for * then we can use this ticket for the * case.
That patch addresses the @ but not the *
Still does not work for *
OK I revised the ticket to be only for the * character.
that one's not as straight forward as changing the input validation, since the * needs changes in the back-end handling as well.
merged a slightly modified fix from PR 2770
https://github.com/pfsense/pfsense/pull/2770
Not sure that suffices though. Could someone with a Namecheap DDNS setup please try the next 2.3.2 snapshot with and without wildcards?
Tested with pfSense-CE-2.3.2-DEVELOPMENT-amd64-20160702-0342 + Namecheap DDNS using `*` wildcard. Works! Testing was a little rough because the GUI (or PHP?) kept hanging on the status page, but I did check and confirm that the DNS was properly updated.
Thanks Luke.
The delay there is from dyndns's checkip service being very slow to respond, there is another ticket covering that.
Also available in: Atom
