Hi again.
Having about 3.000 q/s on this server I have reached 16384 open files... I
have increased limit for open files to 32768. I guess that we can hardly have
more configured as we are getting close to the number of open ports. Is there
another way how to face this attack? Some kind of thro
Hi everybody.
I have just verified that increasing filedescriptors works. The recommended
value of 4096 may not be enough when you are ISP. I have 16384 now and using
lsof to count open files shows nearly 10.000 open files. The amount of
requests is not high about 2.000 q/sec.
Should I increas
Hello Asif,
to my knowledge, there is no updated RPM. In your case, please look at options
1, 2 and 3 in the blog post at
http://blog.powerdns.com/2014/02/06/related-to-recent-dos-attacks-recursor-configuration-file-guidance/
If you do those things, you do not need a patched package.
Kind rega
Hello Sebastian,
On 06 Feb 2014, at 18:32 , Posner, Sebastian wrote:
> Is there a specific reason (but sheer oversight) for e.g.
> http://downloads.powerdns.com/releases/deb/ not being a apt-compatible
> repository?
> It seems the needed script is even present in that directory but hasn't been
Hi,
Is there a specific reason (but sheer oversight) for e.g.
http://downloads.powerdns.com/releases/deb/ not being a apt-compatible
repository?
It seems the needed script is even present in that directory but hasn't been
executed for about 10 years now.. xD
This would make automatic installat
Hi Bert,
We have use CentOS 6.4 64-bit and install pdns-recursor 3.5.3-1
from monshouwer repository. now we have not face any ddos attack problem.
but we want to update it. have we get any update via repo.
regards,
Murad
On Thu, Feb 6, 2014 at 8:53 PM, bert hubert wrote:
> Hi Winfried,
>
> Th
Hi Winfried,
The updated patch for 3.5.3 can be found on
https://github.com/Habbie/pdns/commit/e24b124a4c7b49f38ff8bcf6926cd69077d16ad8
I'll update the blog too.
Bert
On Thu, Feb 06, 2014 at 02:03:49PM +0100, abang wrote:
> Hello Bert,
>
> Would you also provide the patch for the curr
Hi Aki,
Thanks a lot.
On 02/06/2014 06:26 PM, Aki Tuomi wrote:
Problem is that the error is reported by Zerigo, so you'll have to contact them
to figure out whats wrong.
Feb 6 02:18:03 powerdns pdns[30068]: Received unsuccessful
notification report for 'example.com' from 68.71.141.22:
Hello Bert,
Would you also provide the patch for the current version 3.5.3?
Winfried
Am 06.02.2014 13:10, schrieb bert hubert:
Hi everybody,
Over the past week we've been contacted by a few users reporting their
PowerDNS Recursor became unresponsive under a moderate denial of service
attack,
Problem is that the error is reported by Zerigo, so you'll have to contact them
to figure out whats wrong.
> >>Feb 6 02:18:03 powerdns pdns[30068]: Received unsuccessful
> >>notification report for 'example.com' from 68.71.141.22:53, rcode: 5
This line here says that 68.71.141.22 tells you it w
Hi everybody,
Over the past week we've been contacted by a few users reporting their
PowerDNS Recursor became unresponsive under a moderate denial of service
attack, one which PowerDNS should be expected to weather without issues.
In the course of investigating this issue, we've found that many P
Hi Aki Tuomi,
our slave server is Zerigo.net.
We do not have any access to that slave server for firing that command
which you have given me,
For that testing purpose, I have put our live IP in axfr setting & we
got the result which is shown below,
dig axfr example.com @powerdns.bmsend.com
Hi Sajid,
Please go to your *slave* host and run
dig axfr domain @master
Also, please check your slave and master log files.
Aki
On Thu, Feb 06, 2014 at 03:56:08PM +0530, sajid-gmail wrote:
>
> Hello,
>
> Now, we disabled the IPV6 notification issue,
>
> But still we got below error,
>
>
Hello,
Now, we disabled the IPV6 notification issue,
But still we got below error,
Feb 6 01:54:36 powerdns pdns[28933]: *Received unsuccessful*
notification report for 'example.com' from x.x.x.x:53, rcode: 4
Also,
We would like to mentioned that we had setup Powerdns as a hidden master,
Thanks for your good support,
Now, we disabled the IPV6 notification issue,
But still we got below error,
Feb 6 01:54:36 powerdns pdns[28933]: *Received unsuccessful*
notification report for 'example.com' from x.x.x.x:53, rcode: 4
Also,
We would like to mentioned that we had setup Powerd
On Thu, Feb 06, 2014 at 12:05:56PM +0530, sajid-gmail wrote:
>
> Hello,
>
> I have installed PowerDNS Authoritative Server 3.3 on centos.
>
> when I allow axfr IPs in master then I got follwing below Error,
>
> Feb 5 22:25:30 powerdns pdns[18815]: Error trying to resolve
> 'x:x:x:x::x' for not
16 matches
Mail list logo
