You should first verify that you see the packets arriving to ns1.example.de
- tcpdump should do the work.
Then, enable the query log and ensure that BIND sees the query.
Again, the logs are your friends.
-Original Message-
From: Dotan Cohen [mailto:dotanco...@gmail.com]
Sent: Monday, Oct
What does the logs say?
Is the server chrooted or not?
And I think you want to use "type slave;" for that zone, if this is a secondary
server.
-Original Message-
From: Dotan Cohen [mailto:dotanco...@gmail.com]
Sent: Wednesday, September 29, 2010 12:53 AM
To: Imri Zvik
Cc:
What are you trying to achieve? An empty named.conf file means named will
use defaults for everything, and will probably just work out-of-the-box (as
a simple resolver) so you should give more information about the goal and
problem (including log entries, troubleshooting data etc.).
-Origina
9.4.2,
which worked flawlessly.
-Original Message-
From: JINMEI Tatuya / 神明達哉 [mailto:jin...@isc.org]
Sent: Friday, January 08, 2010 8:55 AM
To: Imri Zvik
Cc: bind-users@lists.isc.org
Subject: Re: File Descriptor limit and malfunction bind
At Tue, 05 Jan 2010 10:36:27 +0200,
Imri Zvik
On Wednesday 06 January 2010 12:49:46 Cathy Almond wrote:
> That's what I think is possibly happening in your case - one potential
> contributing factor being the configuration settings I suggested you
> check for. Somewhat obscure - sorry :-/
No need to be sorry - thank you for taking the time t
On Wednesday 06 January 2010 11:56:13 Cathy Almond wrote:
> Do you use any of the following in your configuration:
>
> transfer-source
> transfer-source-v6
> notify-source
> notify-source-v6
> query-source
> query-source-v6
No :) my configuration is '*source*' free, And anyhow, even if I had it in
Hi,
We've recently upgraded our caching servers to 9.4.3-P4/P3 (2 of them running
9.4.3-P4 and 2 running 9.4.3-P3). Few days ago I've noticed something
strange - When the server is loaded, some queries randomly fails (SERVFAIL).
It seems that only queries for which the answer is NOT cached are
On Sunday 03 January 2010 16:36:06 Ram Akuka wrote:
> i have a high load DNS server running bind 9.4.3 on RH -
> yesterday we experienced a problem with the bind (the bind froze) , and
> when looking at the logs i saw the following error :
> named error: socket: file descriptor exceeds limit (4096
Hi,
After a couple of hours, performance of bind 9.6.1 suddenly drops. While the
server remains responsive, the response time increases, the rate of the
failed queries increases, and CPU/load average usage increases. Restarting
named solves the problem.
I cannot find anything useful in the
9 matches
Mail list logo