message 로그 좀 봐 주세요..
작성자 정보
- 정관 작성
- 작성일
컨텐츠 정보
- 840 조회
- 0 추천
- 목록
본문
아래와 같이 계속 생깁니다.
제가 서버 셋팅을 잘못 한건가요...
조언 부탁합니다...
Jun 11 17:54:19 ns1 named[974]: lame server resolving '8.137.99.61.in-addr.arpa' (in '137.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 17:54:20 ns1 named[974]: lame server resolving '8.137.99.61.in-addr.arpa' (in '137.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 17:54:21 ns1 named[974]: lame server resolving '8.137.99.61.in-addr.arpa' (in '137.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 17:55:54 ns1 named[974]: lame server resolving '8.137.99.61.in-addr.arpa' (in '137.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 18:14:20 ns1 named[974]: lame server resolving '22.164.249.61.in-addr.arpa' (in '164.249.61.in-addr.arpa'?): 203.240.193.11#53
Jun 11 18:20:38 ns1 named[974]: lame server resolving '150.96.124.210.in-addr.arpa' (in '96.124.210.in-addr.arpa'?): 164.124.101.31#53
Jun 11 18:21:02 ns1 last message repeated 11 times
Jun 11 18:26:51 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:26:51 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:26:54 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:26:54 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:26:57 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:26:57 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:00 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:00 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:03 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:03 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:04 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:04 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:06 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:06 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:07 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:07 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:08 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:08 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:11 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:11 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:50 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:50 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:53 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:53 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:56 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:56 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:56 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:56 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:27:59 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:27:59 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:28:00 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:28:00 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:28:54 ns1 named[974]: lame server resolving '22.164.249.61.in-addr.arpa' (in '164.249.61.in-addr.arpa'?): 203.240.193.11#53
Jun 11 18:28:56 ns1 named[974]: lame server resolving '22.164.249.61.in-addr.arpa' (in '164.249.61.in-addr.arpa'?): 203.251.201.1#53
Jun 11 18:33:54 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 18:33:54 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:33:57 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.195#53
Jun 11 18:33:57 ns1 named[974]: lame server resolving '19.154.98.61.in-addr.arpa' (in '154.98.61.in-addr.arpa'?): 61.78.58.230#53
Jun 11 19:14:09 ns1 named[974]: lame server resolving '106.29.101.210.in-addr.arpa' (in '29.101.210.in-addr.arpa'?): 203.240.193.11#53
Jun 11 19:22:10 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:22:11 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:22:14 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:22:14 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:22:29 ns1 named[974]: lame server resolving '232.239.249.61.in-addr.arpa' (in '239.249.61.in-addr.arpa'?): 203.240.193.11#53
Jun 11 19:24:00 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:24:00 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:24:03 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:24:04 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:24:40 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:24:40 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:24:41 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:24:41 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:24:43 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:24:43 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:24:44 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:24:44 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:25:19 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:25:19 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:25:22 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.100#53
Jun 11 19:25:24 ns1 named[974]: lame server resolving '196.202.99.61.in-addr.arpa' (in '202.99.61.in-addr.arpa'?): 210.117.65.2#53
Jun 11 19:40:17 ns1 named[974]: lame server resolving '232.239.249.61.in-addr.arpa' (in '239.249.61.in-addr.arpa'?): 203.240.193.11#53
Jun 11 20:06:49 ns1 named[974]: lame server resolving 'ns.aminet.co.kr' (in 'aminet.CO.kr'?): 203.240.193.11#53
Jun 11 20:18:00 ns1 named[974]: lame server resolving '2.132.190.211.in-addr.arpa' (in '132.190.211.in-addr.arpa'?): 203.251.201.1#53
Jun 11 20:23:39 ns1 named[974]: lame server resolving '141.150.124.210.in-addr.arpa' (in '150.124.210.in-addr.arpa'?): 164.124.101.31#53
Jun 11 20:23:42 ns1 named[974]: lame server resolving '141.150.124.210.in-addr.arpa' (in '150.124.210.in-addr.arpa'?): 164.124.101.31#53
Jun 11 20:26:20 ns1 named[974]: lame server resolving '242.89.33.211.in-addr.arpa' (in '89.33.211.in-addr.arpa'?): 210.117.65.100#53
Jun 11 20:26:20 ns1 named[974]: lame server resolving '242.89.33.211.in-addr.arpa' (in '89.33.211.in-addr.arpa'?): 210.117.65.2#53
Jun 11 20:26:24 ns1 named[974]: lame server resolving '242.89.33.211.in-addr.arpa' (in '89.33.211.in-addr.arpa'?): 210.117.65.100#53
Jun 11 20:26:24 ns1 named[974]: lame server resolving '242.89.33.211.in-addr.arpa' (in '89.33.211.in-addr.arpa'?): 210.117.65.2#53
Jun 11 20:26:27 ns1 named[974]: lame server resolving '242.89.33.211.in-addr.arpa' (in '89.33.211.in-addr.arpa'?): 210.117.65.100#53
관련자료
-
이전
-
다음