Hi there,
On Tue, 9 May 2017, Paul Seward wrote:
... I'm not so much asking for a fix as asking how I can find more
information. ...
grep '\(released\|security\)' bind-9.10.5/CHANGES | head -n 90
--
73,
Ged.
___
Please visit https://lists.isc.org/
Paul Seward wrote:
>
> I thought I might get that sort of response, I'm not so much asking for a
> fix as asking how I can find more information.
It'll be one of the 42 CVEs in the table at the top of this page:
https://kb.isc.org/article/AA-00913/74/BIND-9-Security-Vulnerability-Matrix.html
I t
Hi Jim,
I thought I might get that sort of response, I'm not so much asking for a
fix as asking how I can find more information.
We're in the process of migrating from this version of bind to something
more recent - and may well use this incident as a lever to speed up some of
the political hurdl
Hi all,
We've got some recursive-only servers running bind 9.8.1 on CentOS 6.9
(using 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.1 from the CentOS repos)
They've unexpectedly quit a couple of times in the last month, leaving
errors like this in the logs:
09-May-2017 09:12:56.747 dnssec: info: validati
Ok , Thank you
2014-12-01 10:49 GMT+00:00 Tony Finch :
> Kaouthar Chetioui wrote:
> >
> > I don't find any name of source file (like message.c or name.c) or name
> of
> > function in this log file, so I can't understand excatly the process of
> > resolution for dig command.
>
> The log module gi
Kaouthar Chetioui wrote:
>
> I don't find any name of source file (like message.c or name.c) or name of
> function in this log file, so I can't understand excatly the process of
> resolution for dig command.
The log module gives you a rough idea of which part of the system emitted
the log message
thank very much for your answer,
I have done it, and when I look at log file, I found a lot of information
like this:
29-Nov-2014 18:09:58.121 general: debug 60: sockmgr 0xb77d7008: watcher got
message -3 for socket 514
29-Nov-2014 18:09:58.121 general: debug 60: sockmgr 0xb77d7008: watcher got
m
Kaouthar Chetioui wrote:
> I want to know the exact path that follows bind to resolve a DNS query
Try running
$ rndc flush
$ rndc trace 11
$ dig www.example.ma
Then look at named's logs which will give you lots of details about
queries, responses, and the parts of BIND involved in the process.
Try option (+nodnssec):
dig www.example.ma +trace +nodnssec
On 11/30/2014 04:40 PM, Matus UHLAR - fantomas wrote:
> On 30.11.14 11:24, Kaouthar Chetioui wrote:
>> I have already use +trace it gives me the following answer, like this:
>
> no, it doeas not:
>
>> global options: +cmd
>
> you clearly
DIG is used to test/troubleshoot DNS queries. BIND logging is used to
troubleshoot the BIND server itself. Which are you trying to debug?
Also be mindful that BIND will cache any DNS entries it retrieves for
the defined TTLs, so if you dig a second time chances are it's not
going to go to the Inte
On 30.11.14 11:24, Kaouthar Chetioui wrote:
I have already use +trace it gives me the following answer, like this:
no, it doeas not:
global options: +cmd
you clearly did not use +trace here.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to recei
I have already use +trace it gives me the following answer, like this:
global options: +cmd
. 518400 IN NS E.ROOT-SERVERS.NET.
. 518400 IN NS G.ROOT-SERVERS.NET.
. 518400 IN NS D.ROOT-SERVERS.NET.
. 518400 IN NS H.ROOT-SERVERS.NET.
. 518400 IN NS K.ROOT-SERVERS.NET.
. 518400 IN NS B.ROOT-SERVERS.NE
On 30 November 2014 at 11:04, Kaouthar Chetioui
wrote:
> I want to know the exact path that follows bind to resolve a DNS query
Please reply to the list not direct.
The option you are looking for is +trace and needs to be invoked on
the server/system that will be resolving the query for the clie
On 30 November 2014 at 01:22, Kaouthar Chetioui
wrote:
> I want to do full debug for BIND
>
> I use this command: dig www.example.ma -d
What's the problem you are having?
What are you expecting to see when you perform a debug?
What is the real name you are trying to diagnose?
Steve
___
Hi,
I want to do full debug for BIND
I use this command: dig www.example.ma -d
and I have as result:
cancel_lookup()
check_if_done()
list empty
clear_query(0xb77c5010)
sockcount=0
check_next_lookup(0x9915980)
try_clear_lookup(0x9915980)
destroy
freeing server 0xb77c11b0 belonging to 0x9915980
st
In article ,
Tory M Blue wrote:
> Is there a documented method to troubleshoot, debug why a system
> believes that they were unable to get an acceptable results from the
> primary DNS server?
Capture the DNS packets and see if you're sending to the primary in the
first place and what the respo
Hey all,
Well I'm reaching out as I'm at a loss. I have a distributed DNS
architecture with 2 bind-9.7.2-P3 servers behind an F5 Loadbalancer. I
then have another 2 behind another F5 at another location.
My app servers are configured with their resolv.conf looking like:
(please ignore the domain
> alone to do this , so anyone can give some guide how to debug the source
> code =A1=A2 how to modify makefile and test result!
I'll repeat what I said before "make clean" then "make". You don't
need to touch configure or the Makefiles. You just need to do
HI,
I have already analysis where to add new RR,and how to make it works.
But i don't contact automake tool before, so reading so large configure
and makefiles make me feel so bad. I try to understand ,but it just myself
alone to do this , so anyone can give some guide how to debu
19 matches
Mail list logo
