Re: Problem resolving domain

2020-01-27 Thread Mark Andrews
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

Re: Problem resolving domain

2020-01-27 Thread Mauricio Tavares
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

Re: Problem resolving domain

2020-01-27 Thread Stephan von Krawczynski
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

Re: Problem resolving domain

2020-01-27 Thread Barry Margolin
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 >

RE: Problem resolving domain

2020-01-27 Thread Steve Farr via bind-users
Hi, Stephan, If the domain has one working DNS server and one that's broken, but both are in the delegation, then it's somewhat of random luck as to which one you'll try first... If you try the bad one first, then what happens next depends on "how" it's bad. If it's just dead/down, then after a ti

Re: Problem resolving domain

2020-01-27 Thread Reindl Harald
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

Re: Problem resolving domain

2020-01-27 Thread Anand Buddhdev
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

Problem resolving domain

2020-01-27 Thread Stephan von Krawczynski
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,

Re: Why does dig +trace ignore Additional Records?

2020-01-27 Thread Ttttabcd via bind-users
> I am also interested in understanding the reasons behind this > behaviour, especially after reading the following snippet from the > official knowledge base [1]: Thank you for pointing out the official documentation. dig didn't even implement it according to its official documentation!