Hello,
I try to use recursor to resolve names last in the last 24h and get
follow error messages:
-- snip --
Jan 11 08:03:34 stats: 128 outgoing tcp connections, 3 queries running,
74095 outgoing timeouts
Jan 11 08:33:37 stats: 573342 questions, 329288 cache entries, 83016
negative entries,
On Thu, Jan 11, 2007 at 09:53:11AM +0100, thomas polnik wrote:
fyi: I use SuSE 10.1 with pdns-2.9.19-13.4
That is far too old I'm afraid for the recursor. Everybody is strongly urged
to run 3.1.4.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl
Hello,
On Thu, Jan 11, 2007 at 09:53:11AM +0100, thomas polnik wrote:
fyi: I use SuSE 10.1 with pdns-2.9.19-13.4
That is far too old I'm afraid for the recursor. Everybody is strongly urged
to run 3.1.4.
I thank you for this information. Now I use the static rpm-packages from
Hello,
can I ignore messages like Unable to parse packet from remote server
... ?
Here are all messages from recursor since I started it.
-- snip --
# /usr/sbin/pdns_recursor --local-address=127.0.0.1 --local-port=5353
--daemon=no --allow-from=127.0.0.1
Jan 11 11:27:40 Unable to parse
Hi Bert, Thanks for the reply, I should have included more info to start
with...
We are using version 2.9.20 running on red hat. The backends
were compiled with version 3.2.3 gcc. We are not using the recursor.
The custom backend basically replies to any DNS request with a specific
IP
Hello,
I try the trace-option from dig, here is an example:
-- snip --
$ dig www.google.de @130.149.4.20 +trace
; DiG 9.2.4 www.google.de @130.149.4.20 +trace
;; global options: printcmd
. 249661 IN NS L.ROOT-SERVERS.NET.
. 249661 IN
On Thu, Jan 11, 2007 at 04:18:08PM +0100, thomas polnik wrote:
Hello,
I try the trace-option from dig, here is an example:
-- snip --
$ dig www.google.de @130.149.4.20 +trace
+trace and @ do not combine as you expect they would.
But if I try it again to send the same request to recursor,
