네임서버(bind) 가 공격당하는 거 맞나요?
글쓴이: 1day1 / 작성시간: 목, 2007/09/06 - 4:30오후
오랜만에 KLDP 에 오는 군요.
Sep 5 22:35:14 linux named[12558]: FORMERR resolving 'debsmassage.com/MX/IN': 64.20.49.218#53 Sep 5 22:35:15 linux named[12558]: FORMERR resolving 'debsmassage.com/MX/IN': 64.20.39.26#53 Sep 5 22:35:15 linux named[12558]: FORMERR resolving 'intsec.com/MX/IN': 64.14.244.254#53 Sep 5 22:35:15 linux named[12558]: unexpected RCODE (REFUSED) resolving 'teamalbany.com/MX/IN': 204.16.252.6#53 Sep 5 22:35:15 linux named[12558]: FORMERR resolving 'intsec.com/MX/IN': 64.34.46.254#53 Sep 5 22:35:15 linux named[12558]: unexpected RCODE (REFUSED) resolving 'teamalbany.com/MX/IN': 216.66.37.13#53 Sep 5 22:35:18 linux named[12558]: lame server resolving 'ns1.thomascole.net' (in 'ns1.thomascole.NET'?): 213.171.212.50#53 Sep 5 22:35:18 linux named[12558]: lame server resolving 'ns2.thomascole.net' (in 'ns2.thomascole.NET'?): 213.171.212.50#53 Sep 5 22:35:18 linux named[12558]: lame server resolving 'ns1.thomascole.net' (in 'ns1.thomascole.NET'?): 213.171.208.50#53 Sep 5 22:35:18 linux named[12558]: lame server resolving 'ns2.thomascole.net' (in 'ns2.thomascole.NET'?): 213.171.208.50#53 Sep 5 22:35:18 linux named[12558]: FORMERR resolving 'davejanzen.com/MX/IN': 66.45.225.10#53 Sep 5 22:35:19 linux named[12558]: lame server resolving 'ns2.thomascole.net' (in 'ns2.thomascole.NET'?): 213.171.208.50#53 Sep 5 22:35:19 linux named[12558]: lame server resolving 'ns2.thomascole.net' (in 'ns2.thomascole.NET'?): 213.171.212.50#53 Sep 5 22:35:20 linux named[12558]: lame server resolving '198.66.116.211.in-addr.arpa' (in '66.116.211.in-addr.arpa'?): 66.45.244.194#53 Sep 5 22:35:22 linux named[12558]: unexpected RCODE (REFUSED) resolving 'exch.compass-usa.com/A/IN': 12.169.193.125#53 Sep 5 22:35:22 linux named[12558]: FORMERR resolving 'ns2.intertns.com/AAAA/IN': 66.45.244.194#53 Sep 5 22:35:23 linux named[12558]: unexpected RCODE (REFUSED) resolving 'ns.arianeii.be/A/IN': 212.74.77.17#53 Sep 5 22:35:23 linux named[12558]: unexpected RCODE (REFUSED) resolving 'ns.arianeii.be/AAAA/IN': 212.74.77.17#53 Sep 5 22:35:24 linux named[12558]: lame server resolving 'paxton.net' (in 'paxton.NET'?): 209.131.216.102#53 Sep 5 22:35:24 linux named[12558]: FORMERR resolving 'ns1.intertns.com/AAAA/IN': 66.45.244.194#53 Sep 5 22:35:24 linux named[12558]: FORMERR resolving 'ns.intertns.com/AAAA/IN': 66.45.244.194#53 Sep 5 22:35:25 linux named[12558]: lame server resolving 'sellitright.net' (in 'sellitright.NET'?): 161.58.148.98#53 Sep 5 22:35:25 linux named[12558]: lame server resolving 'sellitright.net' (in 'sellitright.NET'?): 161.58.148.38#53 Sep 5 22:35:25 linux named[12558]: unexpected RCODE (REFUSED) resolving 'convergent.com/MX/IN': 12.166.247.4#53 Sep 5 22:35:26 linux named[12558]: unexpected RCODE (REFUSED) resolving 'ns.arianeii.be/AAAA/IN': 212.74.77.17#53 Sep 5 22:35:27 linux named[12558]: unexpected RCODE (SERVFAIL) resolving 'host58-216.pool81116.interbusiness.it/A/IN': 151.99.125.138#53 Sep 5 22:35:27 linux named[12558]: unexpected RCODE (SERVFAIL) resolving 'host58-216.pool81116.interbusiness.it/AAAA/IN': 151.99.125.138#53 Sep 5 22:35:27 linux named[12558]: FORMERR resolving 'boris.infomagic.com/MX/IN': 216.52.184.248#53 Sep 5 22:35:28 linux named[12558]: FORMERR resolving 'boris.infomagic.com/MX/IN': 69.25.142.42#53 Sep 5 22:35:28 linux named[12558]: FORMERR resolving 'boris.infomagic.com/MX/IN': 70.42.37.7#53 Sep 5 22:35:28 linux named[12558]: FORMERR resolving 'boris.infomagic.com/MX/IN': 63.251.92.200#53 Sep 5 22:35:29 linux named[12558]: FORMERR resolving 'boris.infomagic.com/MX/IN': 64.74.96.225#53 Sep 5 22:35:29 linux named[12558]: lame server resolving 'soccermate.com' (in 'soccermate.com'?): 213.167.152.52#53 Sep 5 22:35:30 linux named[12558]: lame server resolving 'soccermate.com' (in 'soccermate.com'?): 213.167.152.54#53 Sep 5 22:35:31 linux named[12558]: lame server resolving 'internet.canadorec.on.ca' (in 'canadorec.on.ca'?): 209.105.192.122#53 Sep 5 22:35:32 linux named[12558]: unexpected RCODE (SERVFAIL) resolving 'starmiles.it/MX/IN': 193.205.245.8#53
네임서버가 죽는 현상(crash) 이 있어 로그를 살펴보니 무지막지한 이런 로그들이 남아있네요.
해당 도메인은 우리쪽 네임서버에 없는 것들인데, 저런것이 남을 일이 없을 것 같은데.
공격당하는 것 맞나요?
네임서버가 요즘들어 자주죽는데, 해킹시도 혹은 DDOS ? 인지. 업그레이드라도 해봐야 겠습니다.
Forums:
일단 해당로그는
일단 해당로그는 named.conf 의 option 항목에 allow-recursion 처리를 해주니 남지는 않네요.
F/OSS 가 함께하길.. (F/OSS서포터즈 : [[FOSS/Supporters]], [[FOSS/Supporters/Group]])
- 추천 프로젝트 : 추천하기 힘드시나요? 추천 꾹 눌러주세요! -
댓글 달기