Hi,
maybe just co-incidence, but I also had my recursor die yesterday on
me with exactly the same error message. Restarting the recursor fixed
the error:
Aug 9 01:50:46 dilbert pdns_recursor[3395]: Failed to update .
records, RCODE=2
Aug 9 01:53:42 dilbert pdns_recursor[3395]: Failed to
On 8/9/07, bert hubert <[EMAIL PROTECTED]> wrote:
> 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
On Thu, Aug 09, 2007 at 11:07:22PM +0200, thomas polnik wrote:
> > Otherwise PowerDNS can't receive answers to the questions it is sending out!
> Yes, this is correct, sorry, my mistake. If I would make this changes, I
> would see it ... very fast :)
But I understand this was not the case when yo
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
>> iptable
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
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 a
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 d
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 li
Dear Andrew,
> I have only ever seen this when the firewall is preventing the
> recursor from communicating.
> Have you made any recent Firewall adjustments ?
No, I did not change the firewall.
> Tried it by dropping the firewall ?
This was my first idea. I got this message on two recursor
insta
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 hav
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 mes
MAIL PROTECTED] On Behalf Of bert hubert
> Sent: Thursday, August 09, 2007 9:17 PM
> To: thomas polnik
> Cc: pdns-users@mailman.powerdns.com
> Subject: Re: [Pdns-users] recursor can't refresh the . records
>
> On Thu, Aug 09, 2007 at 09:46:35AM +0200, thomas polnik wrote:
>
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?
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 ever
-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]: Fail
15 matches
Mail list logo
