作者 主題: LogWatch 中的 message ...about BIND..  (閱讀 1739 次)

0 會員 與 1 訪客 正在閱讀本文。

myz

  • 活潑的大學生
  • ***
  • 文章數: 433
    • 檢視個人資料
LogWatch 中的 message ...about BIND..
« 於: 2002-03-31 02:33 »
--------------------- Named Begin ------------------------

**Unmatched Entries**
  /etc/named.conf:19: parse error near allow-update: 2 Time(s)
  /etc/named.conf:8: parse error near }: 5 Time(s)
  command channel listening on 127.0.0.1#953: 5 Time(s)
  lame server on '1.4.134.140.in-addr.arpa' (in '134.140.in-addr.arpa'?): 140.111.1.2#53: 1 Time(s)
  lame server on '1.56.192.192.in-addr.arpa' (in '192.192.in-addr.arpa'?): 192.83.166.11#53: 1 Time(s)
  lame server on '11.248.79.211.in-addr.arpa' (in '248.79.211.in-addr.arpa'?): 211.79.241.2#53: 1 Time(s)
  lame server on '12.250.168.203.in-addr.arpa' (in '250.168.203.in-addr.arpa'?): 210.80.60.1#53: 1 Time(s)
  lame server on '129.128-255.171.212.63.in-addr.arpa' (in '128-255.171.212.63.in-addr.arpa'?): 216.34.197.101#53: 1 Time(s)
  lame server on '133.15.232.194.in-addr.arpa' (in '232.194.in-addr.arpa'?): 193.0.0.193#53: 1 Time(s)
  lame server on '142.25.44.211.in-addr.arpa' (in '25.44.211.in-addr.arpa'?): 210.180.98.69#53: 2 Time(s)
  lame server on '142.25.44.211.in-addr.arpa' (in '25.44.211.in-addr.arpa'?): 210.94.0.7#53: 2 Time(s)
  lame server on '168.198.98.202.in-addr.arpa' (in '198.98.202.in-addr.arpa'?): 202.98.96.68#53: 1 Time(s)
  lame server on '175.11.73.211.in-addr.arpa' (in '11.73.211.in-addr.arpa'?): 211.73.31.7#53: 2 Time(s)
  lame server on '175.11.73.211.in-addr.arpa' (in '11.73.211.in-addr.arpa'?): 211.73.31.8#53: 2 Time(s)
  lame server on '227.119.97.61.in-addr.arpa' (in '119.97.61.in-addr.arpa'?): 61.97.112.19#53: 2 Time(s)
  lame server on '227.119.97.61.in-addr.arpa' (in '119.97.61.in-addr.arpa'?): 61.97.112.94#53: 2 Time(s)
  lame server on '248.223.125.203.in-addr.arpa' (in '125.203.in-addr.arpa'?): 202.12.28.131#53: 1 Time(s)
  lame server on '249.151.130.140.in-addr.arpa' (in '151.130.140.in-addr.arpa'?): 140.123.1.2#53: 1 Time(s)
  lame server on '249.151.130.140.in-addr.arpa' (in '151.130.140.in-addr.arpa'?): 140.123.5.2#53: 1 Time(s)
  lame server on '249.151.130.140.in-addr.arpa' (in '151.130.140.in-addr.arpa'?): 140.123.7.2#53: 1 Time(s)
  lame server on '249.151.130.140.in-addr.arpa' (in '151.130.140.in-addr.arpa'?): 163.28.100.2#53: 1 Time(s)
  lame server on '250.24.75.203.in-addr.arpa' (in '24.75.203.in-addr.arpa'?): 61.218.171.82#53: 1 Time(s)
  lame server on '3.99.103.202.in-addr.arpa' (in '99.103.202.in-addr.arpa'?): 202.103.96.68#53: 1 Time(s)
  lame server on '3.99.103.202.in-addr.arpa' (in '99.103.202.in-addr.arpa'?): 202.96.0.133#53: 1 Time(s)
  lame server on '3.99.103.202.in-addr.arpa' (in '99.103.202.in-addr.arpa'?): 202.96.199.133#53: 1 Time(s)
  lame server on '35.31.200.211.in-addr.arpa' (in '31.200.211.in-addr.arpa'?): 210.180.98.69#53: 39 Time(s)
  lame server on '35.31.200.211.in-addr.arpa' (in '31.200.211.in-addr.arpa'?): 210.94.0.7#53: 39 Time(s)
  lame server on '42.89.57.217.in-addr.arpa' (in '89.57.217.in-addr.arpa'?): 151.99.125.2#53: 2 Time(s)
  lame server on '55.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.160.13#53: 10 Time(s)
  lame server on '55.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.161.13#53: 10 Time(s)
  lame server on '58.57.57.217.in-addr.arpa' (in '57.57.217.in-addr.arpa'?): 151.99.125.2#53: 2 Time(s)
  lame server on '58.57.57.217.in-addr.arpa' (in '57.57.217.in-addr.arpa'?): 151.99.250.2#53: 2 Time(s)
  lame server on '65.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.160.13#53: 6 Time(s)
  lame server on '65.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.161.13#53: 6 Time(s)
  lame server on '66.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.160.13#53: 4 Time(s)
  lame server on '66.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.161.13#53: 4 Time(s)
  lame server on '67.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.160.13#53: 4 Time(s)
  lame server on '67.173.129.216.in-addr.arpa' (in '173.129.216.in-addr.arpa'?): 216.129.161.13#53: 4 Time(s)
  lame server on '68.96.98.202.in-addr.arpa' (in '96.98.202.in-addr.arpa'?): 202.96.0.133#53: 1 Time(s)
  lame server on '69.94.9.216.in-addr.arpa' (in '94.9.216.in-addr.arpa'?): 199.0.216.222#53: 1 Time(s)
  lame server on '69.94.9.216.in-addr.arpa' (in '94.9.216.in-addr.arpa'?): 205.177.10.10#53: 1 Time(s)
  lame server on '70.16.78.211.in-addr.arpa' (in '16.78.211.in-addr.arpa'?): 211.78.1.1#53: 2 Time(s)
  lame server on '70.16.78.211.in-addr.arpa' (in '16.78.211.in-addr.arpa'?): 211.78.1.2#53: 2 Time(s)
  lame server on '72.89.109.140.in-addr.arpa' (in '89.109.140.in-addr.arpa'?): 140.109.88.88#53: 2 Time(s)
  lame server on '98.42.61.61.in-addr.arpa' (in '42.61.61.in-addr.arpa'?): 211.78.1.1#53: 2 Time(s)
  lame server on '98.42.61.61.in-addr.arpa' (in '42.61.61.in-addr.arpa'?): 211.78.1.2#53: 2 Time(s)
  lame server on 'ns.cqcqptt.net.cn' (in 'cqcqptt.net.cn'?): 61.128.128.68#53: 1 Time(s)
  loading configuration from '/etc/named.conf': 18 Time(s)
  loading configuration: failure: 7 Time(s)
  no IPv6 interfaces found: 11 Time(s)
  no longer listening on 127.0.0.1#53: 5 Time(s)
  no longer listening on 61.221.203.12#53: 5 Time(s)
  running: 5 Time(s)
  shutting down: 5 Time(s)
  starting BIND 9.1.3 -u named: 12 Time(s)
  the default for the 'auth-nxdomain' option is now 'no': 11 Time(s)
  using 2 CPUs: 12 Time(s)

---------------------- Named End -------------------------


每天都有一堆這樣的東西, 可是我看不懂, 能幫我解讀一下??

Anonymous

  • 訪客