starred/nsupdate.info-nsupdate-info

Fork 0

mirror of https://github.com/nsupdate-info/nsupdate.info.git synced 2026-04-25 08:35:56 +03:00

[GH-ISSUE #207] pfsense "result match" #184

New issue

Closed

opened 2026-02-26 09:36:23 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 09:36:23 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (May 26, 2015).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/207

A user reported this about the example pfsense configuration we show after adding a new host:
"""
I use pfSense and had the "Result match" code copy-pasted to my pfSense configuration. However, in pfSense one must escape the vertical bar (i.e. |) with a backslash (i.e. ). I now added the "" and believe all is well now.
"""

What we currently show is: Result match: good|nochg

What the user suggests is: Result match: good\|nochg

Can somebody please comment on what is correct? I personally don't use pfsense and can't test it.

Originally created by @ThomasWaldmann on GitHub (May 26, 2015). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/207 A user reported this about the example pfsense configuration we show after adding a new host: """ I use pfSense and had the "Result match" code copy-pasted to my pfSense configuration. However, in pfSense one must escape the vertical bar (i.e. |) with a backslash (i.e. ). I now added the "\" and believe all is well now. """ ``` What we currently show is: Result match: good|nochg What the user suggests is: Result match: good\|nochg ``` Can somebody please comment on what is correct? I personally don't use pfsense and can't test it.

kerem

2026-02-26 09:36:23 +03:00

closed this issue
added the
task

bug
labels

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Dec 28, 2015):

as there was no feedback yet, I'll shift this to next milestone.

@ThomasWaldmann commented on GitHub (Dec 28, 2015): as there was no feedback yet, I'll shift this to next milestone.

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@lebeno commented on GitHub (Mar 27, 2016):

I have the same error and performed some tests. Still no success.

pfSense System logs when updating:
php-fpm[7041]: /services_dyndns_edit.php: phpDynDNS: (Error) Result did not match.

I changed Result Match from good|nochg to good\|nochg but same result.

It looks like the dynamic update is registered at nsupdate.info, but the parsing of the result on pfSense fails.

@lebeno commented on GitHub (Mar 27, 2016): I have the same error and performed some tests. Still no success. pfSense System logs when updating: `php-fpm[7041]: /services_dyndns_edit.php: phpDynDNS: (Error) Result did not match.` I changed Result Match from `good|nochg` to `good\|nochg` but same result. It looks like the dynamic update is registered at nsupdate.info, but the parsing of the result on pfSense fails.

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Mar 27, 2016):

Did you also try "good|nochg"?

BTW, nsupdate.info returns standard return strings as specified by the dyndns "standard", so it should be not too hard to configure pfsense for it (assuming that it works in principle).

@ThomasWaldmann commented on GitHub (Mar 27, 2016): Did you also try "good|nochg"? BTW, nsupdate.info returns standard return strings as specified by the dyndns "standard", so it should be not too hard to configure pfsense for it (assuming that it works in principle).

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@lebeno commented on GitHub (Mar 28, 2016):

Yes, I tried good|nochg and same result. good\nochg was a typo in my comment.

@lebeno commented on GitHub (Mar 28, 2016): Yes, I tried `good|nochg` and same result. `good\nochg` was a typo in my comment.

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Mar 28, 2016):

maybe it tries to do a full match. the results looks like "good 1.2.3.4" or "nochg 1.2.3.4".

@ThomasWaldmann commented on GitHub (Mar 28, 2016): maybe it tries to do a full match. the results looks like "good 1.2.3.4" or "nochg 1.2.3.4".

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@lebeno commented on GitHub (Mar 29, 2016):

Looks like it is indeed necessary to do a full match, the actual Result Match string that works is
good %IP%|nochg %IP%

Tested on pfSense 2.2.6-RELEASE. Got inspiration from this post: http://www.slicesofcomputer.com/2015/01/make-google-domains-dyndns-work-with.html

I suggest correcting the "Result String" in the pfSense section of nsupdate.info "How to configure automated dynamic DNS updates?".

@lebeno commented on GitHub (Mar 29, 2016): Looks like it is indeed necessary to do a full match, the actual Result Match string that works is `good %IP%|nochg %IP%` Tested on pfSense 2.2.6-RELEASE. Got inspiration from this post: http://www.slicesofcomputer.com/2015/01/make-google-domains-dyndns-work-with.html I suggest correcting the "Result String" in the pfSense section of nsupdate.info "How to configure automated dynamic DNS updates?".

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Mar 30, 2016):

TODO: add working string to the configuration help it shows after adding a host.

@ThomasWaldmann commented on GitHub (Mar 30, 2016): TODO: add working string to the configuration help it shows after adding a host.

kerem commented

2026-02-26 09:36:24 +03:00

Author

Owner

@FreeMinded commented on GitHub (May 31, 2016):

Fixed with this commit https://github.com/nsupdate-info/nsupdate.info/pull/263

@FreeMinded commented on GitHub (May 31, 2016): Fixed with this commit https://github.com/nsupdate-info/nsupdate.info/pull/263