Both servers are broken. One fails to implement DNS COOKIE (RFC 7873)
correctly. Note that the "Client COOKIE mismatch" is reported. Named rejects
the response because the client cookie does not match that sent to the server.
The response looks like someone trying to spoof the response. The o
On Mon, Jan 27, 2020 at 10:27 AM Stephan von Krawczynski
wrote:
>
> Hello all,
>
> I ran across a question I did not really expect. I am using bind 9.14.1 as
> normal, standalone nameserver. When trying to resolve a certain domain I get a
> SERVFAIL (with nslookup). Deeper inspection of the proble
On Mon, 27 Jan 2020 16:36:42 +0100
Anand Buddhdev wrote:
> On 27/01/2020 16:26, Stephan von Krawczynski wrote:
>
> Hi Stephan,
>
> > I would have expected that bind finds the domain by using the working
> > nameserver and ignoring the dead one. But obviously it does not.
> > Did I misconfigure
In article ,
Stephan von Krawczynski wrote:
> Hello all,
>
> I ran across a question I did not really expect. I am using bind 9.14.1 as
> normal, standalone nameserver. When trying to resolve a certain domain I get a
> SERVFAIL (with nslookup). Deeper inspection of the problem shows that the
>
n letting
it answer incorrectly.
-Original Message-
From: bind-users On Behalf Of Stephan von
Krawczynski
Sent: Monday, January 27, 2020 10:27 AM
To: bind-us...@isc.org
Subject: Problem resolving domain
Hello all,
I ran across a question I did not really expect. I am using bind 9.14.1 as
Am 27.01.20 um 16:26 schrieb Stephan von Krawczynski:
> I ran across a question I did not really expect. I am using bind 9.14.1 as
> normal, standalone nameserver. When trying to resolve a certain domain I get a
> SERVFAIL (with nslookup). Deeper inspection of the problem shows that the
> domain
On 27/01/2020 16:26, Stephan von Krawczynski wrote:
Hi Stephan,
> I would have expected that bind finds the domain by using the working
> nameserver and ignoring the dead one. But obviously it does not.
> Did I misconfigure something? I thought both nameservers should be questioned
> and the firs
Hello all,
I ran across a question I did not really expect. I am using bind 9.14.1 as
normal, standalone nameserver. When trying to resolve a certain domain I get a
SERVFAIL (with nslookup). Deeper inspection of the problem shows that the
domain uses 2 nameservers, where one works perfectly well,
8 matches
Mail list logo