helps a lot.
Thanks
Ray
-Original Message-
From: George Thessalonikefs
Sent: 27 July 2020 15:51
To: RayG
Cc: unbound-users@lists.nlnetlabs.nl
Subject: Re: Unbound randomly fails to resolve names
Hi Ray,
On 23/07/2020 15:23, RayG wrote:
> Hi George,
>
> OK thanks for the confir
0::@853#Dns.google
> forward-addr: 2001:4860:4860::8844@853#Dns.google
> # DNS Privacy
> forward-addr: 94.130.110.185@853#ns1.dnsprivacy.at
> forward-addr: 94.130.110.178@853#ns2.dnsprivacy.at
>
> Thanks again for the information it has been useful to me and I suspec
Hi George,
Following on from my last reply, having set up a number of forwarders and
turned on the (use-caps-for-id: yes) I had this in the log file for
sqrl.ver.grc.com (see below)
I think we see a "Capsforid: starting fallback" 3 times and then "Capsforid:
reply is equal. go to next fallbac
53#ns1.dnsprivacy.at
forward-addr: 94.130.110.178@853#ns2.dnsprivacy.at
Thanks again for the information it has been useful to me and I suspect others.
Ray
-Original Message-
From: George Thessalonikefs
Sent: 22 July 2020 17:30
To: RayG
Cc: unbound-users@lists.nlnetlabs.nl
Subject: Re:
odule. It had nothing to do with upstream connections, tcp
connections, or DoT and if unbound is not compiled with the ipsecmod,
the code should be identical to the 1.9.4 version.
Best regards,
-- George
>
> I hope that helps.
>
> Thanks for any further information/comments
>
&g
ubject: Re: Unbound randomly fails to resolve names
Hi Ray, Andi,
I see from Ray's log that use-caps-for-id: is enabled.
I also see that the forwarding resolvers used seem to have an issue with
0x20 replies (use-caps-for-id related).
For example:
When unbound asks for an.ExaMple.domAin.NeT an
Hi George,
I'm also suffering from this strange fail -- since years.
It's become noticeable better with 1.9.x though.
Ususally, if the result is not in the cache, it takes a minute or two
to finally get the resolution. Not sure if it's become better with the
update or with changing dns servers. I
Hi Ray, Andi,
I see from Ray's log that use-caps-for-id: is enabled.
I also see that the forwarding resolvers used seem to have an issue with
0x20 replies (use-caps-for-id related).
For example:
When unbound asks for an.ExaMple.domAin.NeT and the record is not cached
in the forwarder, the answer
Subject: Re: Unbound randomly fails to resolve names Date: Fri, Jul 17, 2020 at
11:40:30PM +0200 Quoting Andi via Unbound-users
(unbound-users@lists.nlnetlabs.nl):
> As of now (23:34) two unbound instances fail to resolve cloudflare.net NS
> and anything using it as DNS service.
>
Zitat von RayG via Unbound-users :
I did as requested and sent things in plain text but I have still had no
response from anyone?
This issue is causing me issues every day and I would just like to get it
resolved one way or another.
Any help or suggestions as to why Unbound is failing random
On 7/11/20 8:33 AM, RayG via Unbound-users wrote:
Is no one else seeing this issue?
I have seen no replies from nlnetlabs or anyone else.
...
*From:*RayG
*Sent:* 01 July 2020 15:31
*To:* unbound-us...@nlnetlabs.nl
*Subject:* Unbound randomly fails to resolve names
...
It contains a short
fails to resolve names
Hi,
After resolving my performance issues in the thread :
"Unbound can be made unresponsive when using DoT" in the June archives.
I now need to understand why Unbound randomly fails to resolve names and
causes various processes on my system to work i
Hi,
After resolving my performance issues in the thread :
"Unbound can be made unresponsive when using DoT" in the June archives.
I now need to understand why Unbound randomly fails to resolve names and
causes various processes on my system to work incorrectly.
I hope t
13 matches
Mail list logo
