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 days/weeks on end. You may want to try without the firewall.
Ken On Thu, Aug 09, 2007 at 10:20:09PM +0200, thomas wrote: > 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 > installations, the systems are installed on different locations. If I > restarted the recursors, the recursor updated the hint file and worked > for 2 or 3 hours fine and then I got the same message. So I think, our > firewall did not drop any packets. > > Best regards, > thomas polnik. > > _______________________________________________ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > http://mailman.powerdns.com/mailman/listinfo/pdns-users > _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users