[GH-ISSUE #151] pfsense does not work / only updates once? #139

New issue

Closed

opened 2026-02-26 09:36:01 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @ThomasWaldmann on GitHub (Jun 27, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/151

momo said that it doesn't update.

Originally created by @ThomasWaldmann on GitHub (Jun 27, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/151 momo said that it doesn't update.

kerem

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

closed this issue
added the
needs help

bug
labels

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Jul 19, 2014):

I don't have a running instance of pfsense, so if anybody could confirm that it does (not) work and provide further details, that would be helpful.

@ThomasWaldmann commented on GitHub (Jul 19, 2014): I don't have a running instance of pfsense, so if anybody could confirm that it does (not) work and provide further details, that would be helpful.

kerem commented

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

Author

Owner

@teward commented on GitHub (Aug 29, 2014):

I've got a pfSense box i can test with, I'll do some testing for you (per IRC request for assistance)

@teward commented on GitHub (Aug 29, 2014): I've got a pfSense box i can test with, I'll do some testing for you (per IRC request for assistance)

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Aug 29, 2014):

suspicion from #pfsense irc channel: "if a pfsense box is not directly on the Internet, such as my configuration, it will not do an update after the orginal until system time of 1:01."

@ThomasWaldmann commented on GitHub (Aug 29, 2014): suspicion from #pfsense irc channel: "if a pfsense box is not directly on the Internet, such as my configuration, it will not do an update after the orginal until system time of 1:01."

kerem commented

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

Author

Owner

@teward commented on GitHub (Aug 29, 2014):

There looks like a bug that, unless your WAN IP changes and pfSense sees the change happen (in the case of pfSense directly at the edge of the network), it will not update until the automated cronjob runs, which runs at 01:01 every day. To that end, it will only ever update once every 24 hours unless (a) an update is forced, (b) the WAN IP changes internally, (c) the WAN interface options are changed and it forces an update, or (d) you modify the cron script to run the updater more frequently (however this can cause issues sometimes)

@teward commented on GitHub (Aug 29, 2014): There looks like a bug that, unless your WAN IP changes and pfSense sees the change happen (in the case of pfSense directly at the edge of the network), it will not update until the automated cronjob runs, which runs at 01:01 every day. To that end, it will only ever update once every 24 hours unless (a) an update is forced, (b) the WAN IP changes internally, (c) the WAN interface options are changed and it forces an update, or (d) you modify the cron script to run the updater more frequently (however this can cause issues sometimes)

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Aug 29, 2014):

i added pfSense to the configuration help you get when creating a host.

i also added a note about this issue there, so case closed as far as nsupdate is concerned.
pfSense should implement polling the ip address to notice a change, the crontab is only a workaround.

see there: https://redmine.pfsense.org/issues/2148

@ThomasWaldmann commented on GitHub (Aug 29, 2014): i added pfSense to the configuration help you get when creating a host. i also added a note about this issue there, so case closed as far as nsupdate is concerned. pfSense should implement polling the ip address to notice a change, the crontab is only a workaround. see there: https://redmine.pfsense.org/issues/2148