-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Since 6 month I use the pdns-recursor (pdns-recursor-3.1.3-13 on a
Suse 10.2 system) without any problems. It worked good and fast.
Until yesterday I get follow message every 2 or 3 hours:
Aug 9 07:28:22 resolver01 pdns_recursor[20236]:
On 09/08/07, thomas polnik [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Since 6 month I use the pdns-recursor (pdns-recursor-3.1.3-13 on a
Suse 10.2 system) without any problems. It worked good and fast.
Until yesterday I get follow message every 2 or 3
On Thu, Aug 09, 2007 at 09:46:35AM +0200, thomas polnik wrote:
Until yesterday I get follow message every 2 or 3 hours:
Aug 9 07:28:22 resolver01 pdns_recursor[20236]: Failed to update .
records, RCODE=2
Odd - I haven't seen this happen yet. Did you truly have 6 months of
recursor uptime?
Hi,
i had this problem (bevor i know that i don't need an recursor),
too. but i think this problem was caused of the running firewall.
the problem came at my servers from beginning and not after some
month.
cheers
--
Mit freundlichem Gruß
Dominique H. Schramm (Kfm)
Geschäftsführender Inhaber
We recently had the same issue crop up on our pdns cache servers. We noticed a
few users were pounding the servers pretty good with requests most likely from
a virus on their machines.
The one thing that we noticed was that the pdns process was hitting a file
descriptor limit when this log
Dear Bert,
On Thu, Aug 09, 2007 at 09:46:35AM +0200, thomas polnik wrote:
Until yesterday I get follow message every 2 or 3 hours:
Aug 9 07:28:22 resolver01 pdns_recursor[20236]: Failed to update .
records, RCODE=2
Odd - I haven't seen this happen yet. Did you truly have 6 months
Dear Matt,
We recently had the same issue crop up on our pdns cache servers. We
noticed a few users were pounding the servers pretty good with
requests most likely from a virus on their machines.
The one thing that we noticed was that the pdns process was hitting a
file descriptor limit
This does not rule out the firewall. If there is a problem with
connection establishment and tracking, you could conceivable
exhaust a firewall resource which would have the same symptoms:
the updates work for a period of time and then stop working. Our
recursor instances are working properly for
Dear Kenneth,
This does not rule out the firewall. If there is a problem with
connection establishment and tracking, you could conceivable
exhaust a firewall resource which would have the same symptoms:
the updates work for a period of time and then stop working. Our
recursor instances are
On Thu, Aug 09, 2007 at 10:42:30PM +0200, thomas polnik wrote:
You may want to try without the firewall.
without iptables is perhaps a bad idea :), but I will change it to
iptables -I INPUT 1 -p udp --dport 53 -j ACCEPT
iptables -I INPUT 2 -p tcp --dport 53 -j ACCEPT
This is wrong -
bert hubert schrieb:
On Thu, Aug 09, 2007 at 10:42:30PM +0200, thomas polnik wrote:
You may want to try without the firewall.
Hello,
without iptables is perhaps a bad idea :), but I will change it to
iptables -I INPUT 1 -p udp --dport 53 -j ACCEPT
iptables -I INPUT 2 -p tcp
Hello,
i have some strange problem with CNAME records to an external domain.
For example:
PDNS has example.com which has the following records:
www.example.com A 127.0.0.1
www2.example.com CNAME www.example.com
www3.example.com CNAME www.somwhere-else.com
www --- works
www2 -- works
www3 --
12 matches
Mail list logo
