Re: Unbound fails to resolve some domains

2023-01-28 Thread Stuart Henderson
On 2023-01-27, Rodrigo Readi wrote: > 2023-01-27 7:09 GMT, Otto Moerbeek : >> On Fri, Jan 27, 2023 at 01:26:10AM +, Rodrigo Readi wrote: >> >>> It still happens. But when I kill unbound and start it again, then >>> resolves domains that previously did not resolve. > ... >> >> Increase log

Re: Unbound fails to resolve some domains

2023-01-27 Thread Rodrigo Readi
2023-01-27 22:43 GMT, Zack Newman : >> Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No >> route to host for 2001:4860:4802:36::a port 53 (len 28) >> Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No >> route to host for 2001:4860:4802:32::a port 53 (len

Re: Unbound fails to resolve some domains

2023-01-27 Thread Zack Newman
Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No route to host for 2001:4860:4802:36::a port 53 (len 28) Jan 27 20:59:41 nc10 unbound: [72478:0] error: udp connect failed: No route to host for 2001:4860:4802:32::a port 53 (len 28) Jan 27 20:59:41 nc10 unbound: [72478:0]

Re: Unbound fails to resolve some domains

2023-01-27 Thread Rodrigo Readi
2023-01-27 7:09 GMT, Otto Moerbeek : > On Fri, Jan 27, 2023 at 01:26:10AM +, Rodrigo Readi wrote: > >> It still happens. But when I kill unbound and start it again, then >> resolves domains that previously did not resolve. ... > > Increase log level and look at the logs? Otherwise it's just a

Re: Unbound fails to resolve some domains

2023-01-27 Thread Stuart Henderson
On 2023-01-27, Rodrigo Readi wrote: > BTW, I am using Wifi with weak signal. Perhaps this plays a role? If you have packet loss then possibly, yes. Unbound caches information about hosts that it contacts ("infra-cache") and I'm not sure but this might possibly temporarily stop it from contacting

Re: Unbound fails to resolve some domains

2023-01-26 Thread Otto Moerbeek
On Fri, Jan 27, 2023 at 01:26:10AM +, Rodrigo Readi wrote: > It still happens. But when I kill unbound and start it again, then > resolves domains that previously did not resolve. > > BTW, I am using Wifi with weak signal. Perhaps this plays a role? > > Rod. > > > 2023-01-11 20:06 GMT,

Re: Unbound fails to resolve some domains

2023-01-26 Thread Rodrigo Readi
It still happens. But when I kill unbound and start it again, then resolves domains that previously did not resolve. BTW, I am using Wifi with weak signal. Perhaps this plays a role? Rod. 2023-01-11 20:06 GMT, Rodrigo Readi : > I have unbound 1.16.3 on OpenBSD 7.2, all obtained by succesive

Re: Unbound fails to resolve some domains

2023-01-11 Thread Rodrigo Readi
The only logs I get in /var/log/messages: Jan 11 21:14:27 nc10 unbound: [86313:0] notice: init module 0: validator Jan 11 21:14:27 nc10 unbound: [86313:0] notice: init module 1: iterator But now it is resolving normally. It seems sometimes fails to resolve, sometimes do it. 2023-01-11 20:10

Re: Unbound fails to resolve some domains

2023-01-11 Thread Martin Schröder
Am Mi., 11. Jan. 2023 um 21:06 Uhr schrieb Rodrigo Readi : > It stopped to resolve some domains, for example qwant.com All fine here. > Any Idea what is happening? Not without some logs. Best Martin

Unbound fails to resolve some domains

2023-01-11 Thread Rodrigo Readi
I have unbound 1.16.3 on OpenBSD 7.2, all obtained by succesive upadates (no new installation). It stopped to resolve some domains, for example qwant.com Any Idea what is happening? Thanks Rodrigo