sunmarmot 回復于:2003-02-21 01:00:03 |
嘿嘿??!還有他的高級設置篇在UNIX應用扳子里面...... |
cpss 回復于:2003-02-21 09:20:51 |
由于時間的問題,寫的比較簡單,獻丑了。^_^ |
future00 回復于:2003-03-28 17:07:34 |
我敲入/usr/local/sbin/rndc status時提示:
rndc: connect failed: connection refused 謝謝告訴我是什么原因。 |
future00 回復于:2003-03-28 17:08:23 |
我敲入/usr/local/sbin/rndc status時提示:
rndc: connect failed: connection refused 謝謝告訴我是什么原因。 |
future00 回復于:2003-03-28 17:18:03 |
還有當我執行 /usr/loal/sbin/named -c /usr/local/bind-9.2.2/named.con 時,我用ps -ef |grep named時看不到進程號。
當我執行 /usr/loal/sbin/named -gc /usr/local/bind-9.2.2/named.con 時,又提示:ignoring config file logging statement due to -g option,這時用ps -ef |grep named能看到進程,并且可以正常使用。 請問是什么原因?謝謝! |
cpss 回復于:2003-03-29 12:17:15 |
只要“-c”應該就可以了。
你執行/usr/loal/sbin/named -c /usr/local/bind-9.2.2/named.conf,如果進程沒有起來,你查一下有什么報錯,具體問題具體解決。 我以前加“-g”是為了能夠直接看到有什么報錯信息,平時運行時我是不加這個參數的。 |
future00 回復于:2003-03-30 22:40:18 |
解決好了,
/usr/loal/sbin/named -u bind -c /usr/local/bind-9.2.2/named.conf & 就可以了,我想應該是權限問題所造成的。 謝謝! |
wangdk 回復于:2003-04-05 13:27:07 |
[color=blue:eb9511c2d8]我謝謝了![/color:eb9511c2d8] |
galaxy1975 回復于:2003-04-07 11:25:17 |
具體到哪兒下載那個name.root呢,
我的DNS現在好像只能找到.cn的域,其他的都找不到 |
Enrique 回復于:2003-04-25 21:39:57 |
tar -xzvpf bind-9.2.2rc1.tar.gz
不行呀 solaris不認識這個文件,有沒有.tar或者.tar.Z |
B2Sun 回復于:2003-05-08 08:22:25 |
表主題: 如何在Openbsd中邦定MAC地址防止IP占用上網
-------------------------------------------------------------------------------- 大家好,我想用OPENBSD3.2建立一個防火墻 PF 我想在防火墻中加入地址邦定功能,: MAC和IP地址邦定一起! 這樣就可以搞定限制了別個不會去冒充上網, 如: IP:192.168.4.1-192.168.4.100 /24這個段可以上網 而 IP: 192.168.4.101-254 /24這個段不可以上網 如果沒有MAC地址和IP邦定的話,那就很難辦了! 如果不能上網的機器在能上網的機器開機之前啟動的話,它就可以上網了,這也是我們不想的事情! 如果 192.168.4.101的機器把自己的IP改為192.168.4.1就可以上網了 如果 我們做了MAC地址邦定的話,就 是改了IP地址也沒有用,不能上網。 (但還是可以冒充IP!如果可以限制不能改IP地址就好了?。?br> |
myxfc 回復于:2003-06-02 17:18:29 |
[quote="B2Sun"]表主題: 如何在Openbsd中邦定MAC地址防止IP占用上網
-------------------------------------------------------------------------------- |
sill 回復于:2003-06-03 11:09:33 |
whoami# /usr/local/sbin/named -gc /usr/local/etc/named.conf
Jun 03 11:00:12.192 starting BIND 9.2.2rc1 -gc /usr/local/etc/named.conf Jun 03 11:00:12.193 using 1 CPU Jun 03 11:00:12.203 loading configuration from '/usr/local/etc/named.conf' Jun 03 11:00:12.204 /usr/local/etc/named.conf:18: unknown option 'zone' Jun 03 11:00:12.204 /usr/local/etc/named.conf:23: unknown option 'zone' Jun 03 11:00:12.205 /usr/local/etc/named.conf:56: unknown option 'zone' Jun 03 11:00:12.205 /usr/local/etc/named.conf:60: unknown option 'zone' Jun 03 11:00:12.205 /usr/local/etc/named.conf:66: unknown option 'key' Jun 03 11:00:12.205 /usr/local/etc/named.conf:71: unknown option 'controls' Jun 03 11:00:12.206 /usr/local/etc/named.conf:75: '}' expected near end of file Jun 03 11:00:12.206 loading configuration: unexpected token Jun 03 11:00:12.206 exiting (due to fatal error) 這是我的named.conf的內容: whoami# cat /usr/local/etc/named.conf # # # # version of an BIND 9.2.2 named.conf # options { directory "/var/namedb"; pid-file "named.pid"; // Setting up secondaries is way easier and the rough picture for this // is explained below. // // If you enable a local name server, don't forget to enter 127.0.0.1 // into your /etc/resolv.conf so this server will be queried first. // Also, make sure to enable it in /etc/rc.conf. zone "." { type hint; file "named.root"; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "localhost.rev"; notify no&& }; // NB: Do not use the IP addresses below, they are faked, and only // serve demonstration/documentation purposes! // // Example secondary config entries. It can be convenient to become // a secondary at least for the zone where your own domain is in. Ask // your .network administrator for the IP address of the responsible // primary. // // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone! // (This is the first bytes of the respective IP address, in reverse // order, with ".IN-ADDR.ARPA" appended.) // // Before starting to setup a primary zone, better make sure you fully // understand how DNS and BIND works, however. There are sometimes // unobvious pitfalls. Setting up a secondary is comparably simpler. // // NB: Don't blindly enable the examples below. :-) Use actual names // and addresses instead. // // NOTE!!! FreeBSD runs bind in a sandbox (see named_flags in rc.conf). // The directory containing the secondary zones must be write aclearcase/" target="_blank" >ccessible // to bind. The following sequence is suggested: // // mkdir /var/namedb/s // chown bind.bind /var/namedb/s // chmod 750 /var/namedb/s zone "173.76.207.in-addr.arpa" in { type master; file "db.207.76.173";notify no; }; // Note difference in style from above to below will accomplish the same thing. zone "bind.com" { type master; file "bind.com.zone"; notify no; }; key "rndc-key" { algorithm hmac-md5; secret "IAVtDRkMo5MObnqyB8e8ug=="; }; controls { inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "rndc-key"; }; }; 我真的不會怎么配置,能給我一個合用的例子嗎?謝謝! |
liyongliang12 回復于:2003-07-15 12:01:17 |
:cry: 請大蝦指點:我輸入命令named status時提示
This may indicate that the remote server is using an older version fo the command protocel controls . This host is not authorized to connect , or the key is invalid. 我的rndc.key文件是這樣的: key "rndc-key" { algorithm hmac-md5; secret "y9xvvfQjdWv9f/Fo7wquBg=="; }; controls { inet 127.0.0.1 port 953 allow { 127.0.0.1; } keys { "rndc-key"; }; }; 請大蝦幫忙,我配DNS好幾天了,老配不好,十分郁悶??!望高人指點迷津?。?!先在此謝過了??! |
rollswen 回復于:2003-07-18 15:30:18 |
我是按照你的方法配置的,當然運行[color=red:95eaf993ad]/usr/local/sbin/named -gc /usr/local/etc/named.conf & [/color:95eaf993ad]后出現一些信息后,將最后顯示一行為“running”。 但光標就停在那里,按回車不出現提示符號,只有按CTRL+C 才可以出現提示符號,但BIND進程也SHUT DOWN了;但不用-gc ,用-c就沒有問題,請幫我一下,我的系統是TRU64 4。0F |
liuwping 回復于:2003-08-07 09:12:18 |
我想問問,在?。遥牛模龋粒裕埂∠虏挥孟聵琼斦f的什么BIND 軟件吧! 那REDHAT?。粒模郑粒危茫拧。樱牛遥郑牛摇。?。1 呢? |
jfcat 回復于:2003-09-11 17:01:50 |
我用系統自帶的DNS,但里面沒有那個named.pid文件
不知道是怎么回事 |
yfhe 回復于:2003-09-15 17:37:55 |
[quote:e6ed95f93b="jfcat"]我用系統自帶的DNS,但里面沒有那個named.pid文件
不知道是怎么回事[/quote:e6ed95f93b] 啟動named后會自動生成的。默認應該是在目錄/var/run/named/下。 |
jfcat 回復于:2003-09-16 10:23:38 |
你是怎么起動的,怎么生成啊
我用上面說的方法起動,顯示說沒那個文件,然后起動就結束了 能不能詳細的講一下 :shock: |
jfcat 回復于:2003-09-16 10:23:55 |
你是怎么起動的,怎么生成啊
我用上面說的方法起動,顯示說沒那個文件,然后起動就結束了 能不能詳細的講一下 :shock: |
jfcat 回復于:2003-09-16 10:29:05 |
你是怎么起動的
我沒那個文件就起動不了 能不能詳細講一下啊 |
lcfzgb 回復于:2004-03-22 18:19:46 |
現在我們可以去設置dns服務器啟動時自動運行,不需要我們開一個窗口去運行它。我們可以在“/etc/rc2.d”目錄下做一個啟動文件,這樣每次服務器啟動時bind都會自動啟動起來。
如何做???偶不知道 |
dcat1 回復于:2004-08-13 15:36:59 |
#
# Aug 13 15:35:02.845 starting BIND 9.2.3rc1 -gc /usr/local/etc/named.conf Aug 13 15:35:02.846 using 1 CPU Aug 13 15:35:02.848 loading configuration from '/usr/local/etc/named.conf' Aug 13 15:35:02.849 listening on IPv4 interface rl0, 192.168.0.11#53 Aug 13 15:35:02.850 listening on IPv4 interface lo0, 127.0.0.1#53 Aug 13 15:35:02.853 command channel listening on 127.0.0.1#953 Aug 13 15:35:02.853 /usr/local/etc/named.conf:39: couldn't add command channel 127.0.0.1#953: address in use Aug 13 15:35:02.853 ignoring config file logging statement due to -g option Aug 13 15:35:02.857 dns_rdata_fromtext: localhost.rev:10: near '@date@': not a valid number Aug 13 15:35:02.858 zone 0.0.127.IN-ADDR.ARPA/IN: loading master file localhost.rev: not a valid number Aug 13 15:35:02.858 zone 0.168.192.in-addr.arpa/IN: loading master file db.192.168.0: file not found Aug 13 15:35:02.858 zone md.com/IN: loading master file md.com.zone: file not found Aug 13 15:35:02.858 running |
dcat1 回復于:2004-08-13 15:38:40 |
#
# Aug 13 15:35:02.845 starting BIND 9.2.3rc1 -gc /usr/local/etc/named.conf Aug 13 15:35:02.846 using 1 CPU Aug 13 15:35:02.848 loading configuration from '/usr/local/etc/named.conf' Aug 13 15:35:02.849 listening on IPv4 interface rl0, 192.168.0.11#53 Aug 13 15:35:02.850 listening on IPv4 interface lo0, 127.0.0.1#53 Aug 13 15:35:02.853 command channel listening on 127.0.0.1#953 Aug 13 15:35:02.853 /usr/local/etc/named.conf:39: couldn't add command channel 127.0.0.1#953: address in use Aug 13 15:35:02.853 ignoring config file logging statement due to -g option Aug 13 15:35:02.857 dns_rdata_fromtext: localhost.rev:10: near '@date@': not a valid number Aug 13 15:35:02.858 zone 0.0.127.IN-ADDR.ARPA/IN: loading master file localhost.rev: not a valid number Aug 13 15:35:02.858 zone 0.168.192.in-addr.arpa/IN: loading master file db.192.168.0: file not found Aug 13 15:35:02.858 zone md.com/IN: loading master file md.com.zone: file not found Aug 13 15:35:02.858 running |