Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-27-2009, 02:11 PM
|
#1
|
LQ Newbie
Registered: Nov 2004
Posts: 27
Rep:
|
Creating a DNS "dead Zone"
I have a situation where a dns client is bombarding my dns server with dummy requests to the point that it seems to be running up my CPU to almost 100% utilization. Due to limitations on the client I am unable to stop the requests from being generated right now.
Is there a way for me to point these dummy requests to a NULL address ( if there is anything like that ) that would prevent further requests ?? or any other solution you would recommend.
The requests usually have the name <whatever>.xyz.com ( so the xyz.com is common to all the dummy requests )
Any help would be appreciated... thanks
|
|
|
04-27-2009, 03:14 PM
|
#2
|
LQ Guru
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
|
In your named.conf:
in options add:
blackhole { blackhats; };
Create and acl called blackhats:
acl "blackhats" {
ip1;ip2;ip3
};
Where you put in the IP addresses of the offending site.
I don't know of a way to do it by domain name as you requested. However, chances are a lot of what you're seeing is all coming from a common network so you can specify that network with CIDR.
|
|
|
04-27-2009, 04:13 PM
|
#3
|
Member
Registered: Jun 2004
Location: Sentado en mi trasero en Chile
Distribution: ArchLinux
Posts: 47
Rep:
|
Also you can manage with iptables and module "recent" it is very cool and scalable.-
You can accept just a few request from any IP for a short time (starting at 60 seconds) if the client reach this few request he will REJECT or DROP until he stop for a 60 seconds. You can add another rule multiplied by 10 the request numbers and drop for an hour.... ETC
Think about it
|
|
|
All times are GMT -5. The time now is 12:10 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|