--- Begin Message ---
> On Aug 20, 2024, at 6:08 PM, Dave Lawrence via dns-operations
> wrote:
>
>
> From: Dave Lawrence
> Subject: Re: [dns-operations] Survey of How to Solving DNS Errors
> Date: August 20, 2024 at 6:08:10 PM PDT
> To: 苗发生
> Cc: "d
--- Begin Message ---
Peter Thomassen writes:
> I still disagree with the characterization of NXDOMAIN as a
> resolution error. That's like characterizing a red street light as a
> driving error.
Just got back from PTO so apologies for the lag. I wanted to heartily
agree with this comment from P
原始邮件-
发件人: "Peter Thomassen"
发送时间:2024-08-15 18:37:58 (星期四)
收件人: "Ralf Weber" , "Xiang Li"
抄送: dns-operations@lists.dns-oarc.net, mf...@mails.tsinghua.edu.cn,
lixi...@nankai.edu.cn
主题: Re: [dns-operations] Survey of How to Solving DNS Errors
Hi.
On 8/15/24 11:25
> On 16 Aug 2024, at 06:40, Fred Morris wrote:
>
> On Thu, 15 Aug 2024, Geoff Huston wrote:
>>
>> As to "what can you do"? there have been a couple of responses to this:
>>
>
> If you run Response Policy Zones (and BIND) you can partially mitigate the
> impact of search lists on this at th
Not anymore. The current QTYPE is NS without the _ prefix.
--
Mark Andrews
> On 16 Aug 2024, at 06:33, Fred Morris wrote:
>
> Qname minimization in relaxed mode intentionally triggers NXDOMAIN looking
> for e.g. _.anything.example.com
>
>> On Thu, 15 Aug 2024, Florian Obser wrote:
>>
>> It
On Thu, 15 Aug 2024, Geoff Huston wrote:
As to "what can you do"? there have been a couple of responses to this:
If you run Response Policy Zones (and BIND) you can partially mitigate the
impact of search lists on this at the recursive resolver by defining
things like *.com.example and *.co
Qname minimization in relaxed mode intentionally triggers NXDOMAIN looking
for e.g. _.anything.example.com
On Thu, 15 Aug 2024, Florian Obser wrote:
It's not a competition but... we are answering 50% NXDOMAIN and that's
considered normal... It's also sad, but what can you do...
__
> On 15 Aug 2024, at 10:39 PM, Florian Obser wrote:
>
> On 2024-08-15 11:25 +02, Ralf Weber wrote:
>> I just logged in to a random server that is doing tens of thousands of
>> requests per second and it had 15% NXDomain queries 1% SERVFAIL and REFUSED
>> and 0.1% FORMERR and that is a typical
On 2024-08-15 11:25 +02, Ralf Weber wrote:
> I just logged in to a random server that is doing tens of thousands of
> requests per second and it had 15% NXDomain queries 1% SERVFAIL and REFUSED
> and 0.1% FORMERR and that is a typical RCODE distribution, and it would
> be impossible to follow and
Hi.
On 8/15/24 11:25, Ralf Weber wrote:
I’m not sure what data you want to get out of that research, but IMHO it is
upfront missing a definition of what a resolution error is.
Question 4 ("What types of DNS resolution errors have you encountered most
frequently?") has NXDOMAIN as one option,
Moin!
On 14 Aug 2024, at 17:27, Xiang Li wrote:
> We are a research team from Tsinghua University and Nankai University. Your
> participation is greatly appreciated and will significantly contribute to
> our research.
>
> Recently, we are conducting a study on DNS resolution errors to understand
>
Dear Participant,
Hello!
We are a research team from Tsinghua University and Nankai University. Your
participation is greatly appreciated and will significantly contribute to
our research.
Recently, we are conducting a study on DNS resolution errors to understand
their occurrence, impact, and ho
12 matches
Mail list logo
