New answers tagged dns
The problem is that you need to drop the traffic before it reaches your network. So even when dropping packets at your server is way too late. The best way to reduce risk is to use packet scrubbing services like Akamai or Cloudfare who have DDoS mitigation techniques in place to prevent this traffic from reaching your network.
We can but... At the point the query makes it to your server it's already too late. Your server will waste its resources trying to do something with the packets and the requests. Even if you have something like iptables drop all connections it's still going to use up all of the bandwidth on the server inbound. Redirecting all traffic someplace else eats up ...
DNS Amplification attacks are very easy to prevent by filtering UDP packets at the edge routers. This is how Cloudflare is able to easily thwart a 300+ gb/s DDoS attack.
Blocking the traffic on the server will not stop the DDoS from eventually saturating its uplink and possibly other links within the network. DNS amplification attacks are all about generating large amounts of bandwidth.
I just did a similar search across some name registrars and it seems that Name.com and GoDaddy both support 2FA, the former using the Verisign/Symantec VIP and the latter using SMS for US numbers only.
If you're looking for privacy, I would say Internet is not for you and that DNS look-up is not the biggest privacy concern. Remember you leave your IP-address - even if that often is a temporarily (dynamic) IP-address lent you by your ISP - with every request you make to a web-server. In addition, your ISP is probably maintaining logs about which of their ...
Top 50 recent answers are included