Loaded core141/831ff0fd from iso . Had DNS over TLS working until I loaded backup from my core139 system. Tried it twice same results where after backup restore DNS is broken no matter how I try the various configuration options on DNS page.
Regards
Wayne
Broken in what way?
On 7 Feb 2020, at 21:22, Mentalic mentalic@cox.net wrote:
Loaded core141/831ff0fd from iso . Had DNS over TLS working until I loaded backup from my core139 system. Tried it twice same results where after backup restore DNS is broken no matter how I try the various configuration options on DNS page.
Regards Wayne
Could no longer open new web sites. Also reverse lookup listing in Dns gui indicates failure.
Regards Wayne
-----Original Message----- From: Michael Tremer [mailto:michael.tremer@ipfire.org] Sent: Friday, February 7, 2020 3:26 PM To: Mentalic Cc: IPFire: Development-List Subject: Re: Testing core141
Broken in what way?
On 7 Feb 2020, at 21:22, Mentalic mentalic@cox.net wrote:
Loaded core141/831ff0fd from iso . Had DNS over TLS working until I
loaded backup from my core139 system. Tried it twice same results where after backup restore DNS is broken no matter how I try the various configuration options on DNS page.
Regards Wayne
Can you find anything in /var/log/messages?
On 7 Feb 2020, at 22:14, Mentalic mentalic@cox.net wrote:
Could no longer open new web sites. Also reverse lookup listing in Dns gui indicates failure.
Regards Wayne
-----Original Message----- From: Michael Tremer [mailto:michael.tremer@ipfire.org] Sent: Friday, February 7, 2020 3:26 PM To: Mentalic Cc: IPFire: Development-List Subject: Re: Testing core141
Broken in what way?
On 7 Feb 2020, at 21:22, Mentalic mentalic@cox.net wrote:
Loaded core141/831ff0fd from iso . Had DNS over TLS working until I
loaded backup from my core139 system. Tried it twice same results where after backup restore DNS is broken no matter how I try the various configuration options on DNS page.
Regards Wayne
Reloaded from Iso again so I could get a time for when I restored backup from core139. Bit of the log file below indicating unbound is failing reading unbound.conf.
Restored backup from core139 which changed DNS protocol from TLS to UDP, I reset to TLS and saved resulting in rDNS failure and no longer looking up web sites.
Feb 8 14:34:04 ipfire syslogd 1.5.1: restart (remote reception). Feb 8 14:35:03 ipfire unbound: [10680:0] info: service stopped (unbound 1.9.6). Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 0: 160 queries, 21 answers from cache, 139 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 0: requestlist max 4 avg 0.690647 exceeded 0 jostled 0 Feb 8 14:35:03 ipfire unbound: [10680:0] info: average recursion processing time 0.129518 sec Feb 8 14:35:03 ipfire unbound: [10680:0] info: histogram of recursion processing times Feb 8 14:35:03 ipfire unbound: [10680:0] info: [25%]=0.0341333 median[50%]=0.0884736 [75%]=0.152137 Feb 8 14:35:03 ipfire unbound: [10680:0] info: lower(secs) upper(secs) recursions Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.000000 0.000001 25 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.008192 0.016384 2 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.016384 0.032768 7 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.032768 0.065536 18 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.065536 0.131072 50 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.131072 0.262144 14 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.262144 0.524288 19 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.524288 1.000000 4 Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 1: 177 queries, 19 answers from cache, 158 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 1: requestlist max 7 avg 0.949367 exceeded 0 jostled 0 Feb 8 14:35:03 ipfire unbound: [10680:0] info: average recursion processing time 0.134711 sec Feb 8 14:35:03 ipfire unbound: [10680:0] info: histogram of recursion processing times Feb 8 14:35:03 ipfire unbound: [10680:0] info: [25%]=0.0340283 median[50%]=0.101648 [75%]=0.193066 Feb 8 14:35:03 ipfire unbound: [10680:0] info: lower(secs) upper(secs) recursions Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.000000 0.000001 26 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.008192 0.016384 3 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.016384 0.032768 10 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.032768 0.065536 13 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.065536 0.131072 49 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.131072 0.262144 37 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.262144 0.524288 17 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.524288 1.000000 2 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 1.000000 2.000000 1 Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 2: 160 queries, 20 answers from cache, 140 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 2: requestlist max 4 avg 0.892857 exceeded 0 jostled 0 Feb 8 14:35:03 ipfire unbound: [10680:0] info: average recursion processing time 0.148368 sec Feb 8 14:35:03 ipfire unbound: [10680:0] info: histogram of recursion processing times Feb 8 14:35:03 ipfire unbound: [10680:0] info: [25%]=0.0311296 median[50%]=0.101425 [75%]=0.211732 Feb 8 14:35:03 ipfire unbound: [10680:0] info: lower(secs) upper(secs) recursions Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.000000 0.000001 23 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.008192 0.016384 3 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.016384 0.032768 10 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.032768 0.065536 11 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.065536 0.131072 42 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.131072 0.262144 26 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.262144 0.524288 20 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.524288 1.000000 4 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 1.000000 2.000000 1 Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 3: 155 queries, 14 answers from cache, 141 recursions, 0 prefetch, 0 rejected by ip ratelimiting Feb 8 14:35:03 ipfire unbound: [10680:0] info: server stats for thread 3: requestlist max 3 avg 0.489362 exceeded 0 jostled 0 Feb 8 14:35:03 ipfire unbound: [10680:0] info: average recursion processing time 0.127968 sec Feb 8 14:35:03 ipfire unbound: [10680:0] info: histogram of recursion processing times Feb 8 14:35:03 ipfire unbound: [10680:0] info: [25%]=0.009216 median[50%]=0.094208 [75%]=0.200704 Feb 8 14:35:03 ipfire unbound: [10680:0] info: lower(secs) upper(secs) recursions Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.000000 0.000001 33 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.004096 0.008192 2 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.008192 0.016384 2 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.016384 0.032768 11 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.032768 0.065536 5 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.065536 0.131072 40 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.131072 0.262144 24 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.262144 0.524288 21 Feb 8 14:35:03 ipfire unbound: [10680:0] info: 0.524288 1.000000 3 Feb 8 14:35:03 ipfire unbound: [10680:0] notice: Restart of unbound 1.9.6. Feb 8 14:35:03 ipfire unbound: [10680:0] fatal error: Could not read config file: /etc/unbound/unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf
Regards Wayne
-----Original Message----- From: Michael Tremer [mailto:michael.tremer@ipfire.org] Sent: Saturday, February 8, 2020 5:19 AM To: Mentalic Cc: IPFire: Development-List Subject: Re: Testing core141
Can you find anything in /var/log/messages?
On 7 Feb 2020, at 22:14, Mentalic mentalic@cox.net wrote:
Could no longer open new web sites. Also reverse lookup listing in Dns gui indicates failure.
Regards Wayne
-----Original Message----- From: Michael Tremer [mailto:michael.tremer@ipfire.org] Sent: Friday, February 7, 2020 3:26 PM To: Mentalic Cc: IPFire: Development-List Subject: Re: Testing core141
Broken in what way?
On 7 Feb 2020, at 21:22, Mentalic mentalic@cox.net wrote:
Loaded core141/831ff0fd from iso . Had DNS over TLS working until I
loaded backup from my core139 system. Tried it twice same results where after backup restore DNS is broken no matter how I try the various configuration options on DNS page.
Regards Wayne
-
Mentalic -
Michael Tremer