Delay in sending WAN DDNS change notices
-
@stephenw10 said in Delay in sending WAN DDNS change notices:
DNS setup? Using Unbound on localhost? I
I have attached images of what I believe are the areas you are referring to
-
Hmm, that should be OK. And I think I conflated some tickets there, you only have one WAN connection?
The WAN is up at that point so Unbound should be able to resolve it but for some reason is failing. Is there anything in the resolver log at that time?
As a test you could try adding dynupdate.no-ip.com as a host override so it will always resolve. That will at least prove that it updates correctly when that is resolvable. Or maybe that it still doesn't resolve if, for example, Unbound is not responding when that runs.
-
@stephenw10 yes only one WAN connection
here is the DNS Resolver log
Jun 30 02:18:27 unbound 60421 [60421:0] info: generate keytag query _ta-4f66. NULL IN
Jun 29 15:08:21 unbound 60421 [60421:0] info: generate keytag query _ta-4f66. NULL IN
Jun 29 14:55:43 unbound 60421 [60421:0] info: generate keytag query _ta-4f66. NULL IN
Jun 29 14:13:45 unbound 60421 [60421:1] info: generate keytag query _ta-4f66. NULL IN
Jun 29 14:12:46 unbound 60421 [60421:0] info: start of service (unbound 1.17.1).
Jun 29 14:12:45 unbound 60421 [60421:0] notice: init module 1: iterator
Jun 29 14:12:45 unbound 60421 [60421:0] notice: init module 0: validator
Jun 29 14:12:45 unbound 60421 [60421:0] notice: Restart of unbound 1.17.1.
Jun 29 14:12:45 unbound 60421 [60421:0] info: 64.000000 128.000000 4
Jun 29 14:12:45 unbound 60421 [60421:0] info: 16.000000 32.000000 1
Jun 29 14:12:45 unbound 60421 [60421:0] info: 8.000000 16.000000 2
Jun 29 14:12:45 unbound 60421 [60421:0] info: 4.000000 8.000000 4
Jun 29 14:12:45 unbound 60421 [60421:0] info: 2.000000 4.000000 2
Jun 29 14:12:45 unbound 60421 [60421:0] info: 1.000000 2.000000 26
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.524288 1.000000 195
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.262144 0.524288 933
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.131072 0.262144 5507
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.065536 0.131072 26293
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.032768 0.065536 17957
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.016384 0.032768 10678
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.008192 0.016384 10493
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.004096 0.008192 11141
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.002048 0.004096 3851
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.001024 0.002048 119
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000512 0.001024 35
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000256 0.000512 28
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000128 0.000256 12
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000064 0.000128 5
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000000 0.000001 2781
Jun 29 14:12:45 unbound 60421 [60421:0] info: lower(secs) upper(secs) recursions
Jun 29 14:12:45 unbound 60421 [60421:0] info: [25%]=0.0117401 median[50%]=0.043517 [75%]=0.0915835
Jun 29 14:12:45 unbound 60421 [60421:0] info: histogram of recursion processing times
Jun 29 14:12:45 unbound 60421 [60421:0] info: average recursion processing time 0.061340 sec
Jun 29 14:12:45 unbound 60421 [60421:0] info: server stats for thread 1: requestlist max 18 avg 0.301109 exceeded 0 jostled 0
Jun 29 14:12:45 unbound 60421 [60421:0] info: server stats for thread 1: 103719 queries, 13652 answers from cache, 90067 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Jun 29 14:12:45 unbound 60421 [60421:0] info: 16.000000 32.000000 13
Jun 29 14:12:45 unbound 60421 [60421:0] info: 8.000000 16.000000 5
Jun 29 14:12:45 unbound 60421 [60421:0] info: 4.000000 8.000000 1
Jun 29 14:12:45 unbound 60421 [60421:0] info: 2.000000 4.000000 13
Jun 29 14:12:45 unbound 60421 [60421:0] info: 1.000000 2.000000 41
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.524288 1.000000 275
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.262144 0.524288 1257
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.131072 0.262144 7251
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.065536 0.131072 32332
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.032768 0.065536 22461
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.016384 0.032768 14640
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.008192 0.016384 14006
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.004096 0.008192 14946
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.002048 0.004096 5488
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.001024 0.002048 155
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000512 0.001024 92
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000256 0.000512 40
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000128 0.000256 17
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000064 0.000128 9
Jun 29 14:12:45 unbound 60421 [60421:0] info: 0.000000 0.000001 3537
Jun 29 14:12:45 unbound 60421 [60421:0] info: lower(secs) upper(secs) recursions
Jun 29 14:12:45 unbound 60421 [60421:0] info: [25%]=0.011035 median[50%]=0.0405869 [75%]=0.0899473
Jun 29 14:12:45 unbound 60421 [60421:0] info: histogram of recursion processing times
Jun 29 14:12:45 unbound 60421 [60421:0] info: average recursion processing time 0.059597 sec
Jun 29 14:12:45 unbound 60421 [60421:0] info: server stats for thread 0: requestlist max 22 avg 0.480953 exceeded 0 jostled 0
Jun 29 14:12:45 unbound 60421 [60421:0] info: server stats for thread 0: 135269 queries, 18690 answers from cache, 116579 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Jun 29 14:12:45 unbound 60421 [60421:0] info: service stopped (unbound 1.17.1).
Jun 29 13:44:41 unbound 60421 [60421:0] info: generate keytag query _ta-4f66. NULL IN
Jun 29 13:12:55 unbound 60421 [60421:0] info: generate keytag query _ta-4f66. NULL IN
Jun 29 12:48:12 unbound 60421 [60421:1] info: generate keytag query _ta-4f66. NULL IN
Jun 29 12:48:12 unbound 60421 [60421:0] info: generate keytag query _ta-4f66. NULL IN -
Hmm, so I wonder if it tries to resolve in the 1s Unbound is restarting. You have system DNS set to only use Unbound locally. You could try setting it back to the defaults so it falls back to using 1.1.1.1 directly if Unbound isn't available. Otherwise testing a host override in Unbound would prove a general connectivity issue.
-
@stephenw10 I have set the DNS Resolution Behavior back to the default setting. We'll see what happens next time....
-
@192-168-1-0 one other question.... what process causes the DDNS update to be sent at 1am?
-
The dyndns update cronjob:
-
@stephenw10 thanks Stephen. That menu was hidden on my pfSense and I had to add it. I appreciate your assistance. We'll see what the next DDNS episode brings,....
-
Yup the cron package is not installed by default, most users never need to see the crontab.
-
@stephenw10 Well that didn't take long. Another IP change today. pfSense correctly, and immediately, updated my DDNS provider and followed up with an email message to me. Looks like setting the DNS Resolution Behavior back to default has resolved my issue. Stephen, thanks so much for sticking with me and walking me through the steps to resolution. It is very much appreciated.
-
Ah, nice. Interesting that Unbound is not able to resolve at that point then.
