我的服务器正被一个巨大的安全DNS淹没。这是在daemon.log和syslog文件中编写大量条目时产生的高I/O。感谢fail2ban,我能够禁止那些IP并使服务器恢复正常。
由于我是Linux学习者,所以我来这里询问有关这方面的一些细节。服务器正在Debian上运行。
下面是一个daemon.log文件的示例:
Jan 27 20:47:43 server named[xxxx]: client 37.110.213.97#51810: query (cache) '2.SecureDNS.AVASt.CoM/TXT/IN' denied
Jan 27 20:47:49 server named[xxxx]: client 154.0.26.150#38513: query (cache) '2.SECUredNs.Avast.cOM/TXT/IN' denied
Jan 27 20:47:50 server named[xxxx]: client 154.0.26.150#33704: query (cache) '2.sEcurEDns.avasT.COm/TXT/IN' denied
Jan 27 20:47:54 server named[xxxx]: client 154.0.26.150#50798: query (cache) '2.sEcUreDns.avasT.com/TXT/IN' denied
Jan 27 20:48:06 server named[xxxx]: client 201.79.137.74#54727: query (cache) '2.SeCuREDnS.AvAST.CoM/TXT/IN' denied
Jan 27 20:48:07 server named[xxxx]: client 201.79.137.74#54735: query (cache) '2.secuReDNs.avaSt.cOM/TXT/IN' denied
Jan 27 20:48:11 server named[xxxx]: client 201.79.100.41#54754: query (cache) '2.SeCUrEDNS.AVAsT.COM/TXT/IN' denied
Jan 27 20:48:12 server named[xxxx]: client 77.147.247.52#62948: query (cache) '2.SecUREdns.AvAsT.COM/TXT/IN' denied发布于 2018-01-28 07:33:20
这不太可能是来自avast安全DNS。更有可能的是,您正在运行一个开放的DNS解析器,而带有僵尸网络的攻击者正试图使用开放解析器将流量定向到DDoS SecureDNS。
https://security.stackexchange.com/questions/178588
复制相似问题