Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Block DNS & NTP Amplification
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Block DNS & NTP Amplification

Hi guys. Do you know any simple way to block these attacks with 1 gbps server.
Is this possible with iptables to limit dns or ntp requests per minute?
Server is not hosting dns server so i think its possible if i upgrade it to 10 gbps maybe. Do anyone have knowledge about it?

Comments

  • tentortentor Member, Patron Provider

    You need DDoS protected uplink otherwise it will simply saturate your connection. You cant mitigate that on your side solely with iptables or another firewall solution.

  • yoursunnyyoursunny Member, IPv6 Advocate

    @Zreind said:
    Server is not hosting dns server

    Then it's not affected by DNS amplification.
    No configuration or firewall needed.

    Thanked by 1babibubebon
  • PacketsDecreaserPacketsDecreaser Member, Patron Provider

    If the Attack is bigger then 1 Gbits (in fact its a amp attack it will be bigger then 1 Gbit) you must search a provider who blocks this traffic for you before it reaches your server.

    If the attack is smaller you can try to minimize the impact with iptables, but mostly it dont help much.

  • PacketsDecreaserPacketsDecreaser Member, Patron Provider

    @Zreind said:
    Hi guys. Do you know any simple way to block these attacks with 1 gbps server.
    Is this possible with iptables to limit dns or ntp requests per minute?
    Server is not hosting dns server so i think its possible if i upgrade it to 10 gbps maybe. Do anyone have knowledge about it?

    Do you have problems with incoming or outgoing attacks ?

  • tentortentor Member, Patron Provider

    @PacketsDecreaser said: outgoing attacks

    It is strange to mitigate OUTGOING attack by increasing port speed :D

  • PacketsDecreaserPacketsDecreaser Member, Patron Provider

    @tentor said:

    @PacketsDecreaser said: outgoing attacks

    It is strange to mitigate OUTGOING attack by increasing port speed :D

    Yeah, but the post from yoursunny confused me :)

  • @yoursunny said:

    @Zreind said:
    Server is not hosting dns server

    Then it's not affected by DNS amplification.
    No configuration or firewall needed.

    But it consumes all the bandwidth that server has. it uses 1 Gbps incoming traffic and loses connection.

    @PacketsDecreaser said:

    @Zreind said:
    Hi guys. Do you know any simple way to block these attacks with 1 gbps server.
    Is this possible with iptables to limit dns or ntp requests per minute?
    Server is not hosting dns server so i think its possible if i upgrade it to 10 gbps maybe. Do anyone have knowledge about it?

    Do you have problems with incoming or outgoing attacks ?

    Generally UDP with incoming, sometimes TCP attacks and both use outgoing/ingoing traffic. I'm also searching for some ddos protection solution like buyvm + path ip address.

  • PacketsDecreaserPacketsDecreaser Member, Patron Provider

    @Zreind said:

    @yoursunny said:

    @Zreind said:
    Server is not hosting dns server

    Then it's not affected by DNS amplification.
    No configuration or firewall needed.

    But it consumes all the bandwidth that server has. it uses 1 Gbps incoming traffic and loses connection.

    @PacketsDecreaser said:

    @Zreind said:
    Hi guys. Do you know any simple way to block these attacks with 1 gbps server.
    Is this possible with iptables to limit dns or ntp requests per minute?
    Server is not hosting dns server so i think its possible if i upgrade it to 10 gbps maybe. Do anyone have knowledge about it?

    Do you have problems with incoming or outgoing attacks ?

    Generally UDP with incoming, sometimes TCP attacks and both use outgoing/ingoing traffic. I'm also searching for some ddos protection solution like buyvm + path ip address.

    We offer protected vServers and remote DDoS protection via gre.
    The Servers are located in germany. We also give a free testserver out, just contact us :smile:

    Check our Website out.

    We also have a website with documentation on how we protect you from attacks

    https://docs.packets-decreaser.net/

    Thanked by 1Zreind
  • yoursunnyyoursunny Member, IPv6 Advocate

    @Zreind said:

    @yoursunny said:

    @Zreind said:
    Server is not hosting dns server

    Then it's not affected by DNS amplification.
    No configuration or firewall needed.

    But it consumes all the bandwidth that server has. it uses 1 Gbps incoming traffic and loses connection.

    Not running DNS server means your server will not be used to attack others.
    It's not possible to block incoming attacks.
    You will unlock the IPv4 nullroute achievement.
    Come to the forum and blame whoever you believe is attacking you.
    The attack will generally stop in a day or two.
    https://lowendtalk.com/discussion/comment/3751697#Comment_3751697

    If you are running a website and the domain is eligible for Cloudflare, you can turn on Cloudflare orange cloud, to keep online during an attack.
    The origin address shall be IPv6, because most incoming attacks would be targeting your IPv4 and then your IPv4 got nullrouted.
    Cloudflare can still reach your origin over IPv6.

    Thanked by 1Zreind
  • @yoursunny said:

    @Zreind said:

    @yoursunny said:

    @Zreind said:
    Server is not hosting dns server

    Then it's not affected by DNS amplification.
    No configuration or firewall needed.

    But it consumes all the bandwidth that server has. it uses 1 Gbps incoming traffic and loses connection.

    Not running DNS server means your server will not be used to attack others.
    It's not possible to block incoming attacks.
    You will unlock the IPv4 nullroute achievement.
    Come to the forum and blame whoever you believe is attacking you.
    The attack will generally stop in a day or two.
    https://lowendtalk.com/discussion/comment/3751697#Comment_3751697

    If you are running a website and the domain is eligible for Cloudflare, you can turn on Cloudflare orange cloud, to keep online during an attack.
    The origin address shall be IPv6, because most incoming attacks would be targeting your IPv4 and then your IPv4 got nullrouted.
    Cloudflare can still reach your origin over IPv6.

    What about routing the dirty traffic to your IPv9 network?
    Mitigate and send it back to me.

  • @Zreind said:

    @yoursunny said:

    @Zreind said:

    @yoursunny said:

    @Zreind said:
    Server is not hosting dns server

    Then it's not affected by DNS amplification.
    No configuration or firewall needed.

    But it consumes all the bandwidth that server has. it uses 1 Gbps incoming traffic and loses connection.

    Not running DNS server means your server will not be used to attack others.
    It's not possible to block incoming attacks.
    You will unlock the IPv4 nullroute achievement.
    Come to the forum and blame whoever you believe is attacking you.
    The attack will generally stop in a day or two.
    https://lowendtalk.com/discussion/comment/3751697#Comment_3751697

    If you are running a website and the domain is eligible for Cloudflare, you can turn on Cloudflare orange cloud, to keep online during an attack.
    The origin address shall be IPv6, because most incoming attacks would be targeting your IPv4 and then your IPv4 got nullrouted.
    Cloudflare can still reach your origin over IPv6.

    What about routing the dirty traffic to your IPv9 network?
    Mitigate and send it back to me.

    I tried this once and the penguins also stole the legitimate traffic and I got no packets at all back.

  • jarjar Patron Provider, Top Host, Veteran

    @tentor said:
    You need DDoS protected uplink otherwise it will simply saturate your connection. You cant mitigate that on your side solely with iptables or another firewall solution.

    Actually I have a one liner that is very effective at handling this solely on the server side:

    ip route add blackhole 0.0.0.0/0

Sign In or Register to comment.