Am Fr., 5. Jan. 2024 um 18:02 Uhr schrieb Roderick :
> Yes. It was mentioned in the list one or two years ago.
> The clock is OK, the internet connection also.
Indeed, this time was the clock!
I set the date to 2023-01-05 ... :)
Now corrected and is OK.
Rod.
Am Fr., 5. Jan. 2024 um 17:44 Uhr schrieb Capitan Cloud :
> Why you say old, is it reoccuring maybe?
Yes. It was mentioned in the list one or two years ago.
The clock is OK, the internet connection also.
> Do you mind to show here the actual content of resolv.conf?
nameserver 127.0.0.1
lookup f
The problem is old. Unbound does not resolve. I upgraded today to OpenBSD 7.4,
before I did not use the Nettop for some months. But when I upgraded
to 7.3 it worked,
today neither before nor after upgrading to 7.4 worked.
I added to the standard configuration file only:
do-ip6: no
log-servfail: y
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 leve
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 28)
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] error:
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
>
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
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, Rod
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 upa
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 GMT
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
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
13 matches
Mail list logo
