| 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地址就好了！）
|
| 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 accessible
// 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
|
我想问问，在 ＲＥＤＨＡＴ９ 下不用下楼顶说的什么ＢＩＮＤ 软件吧！ 那ＲＥＤＨＡＴ ＡＤＶＡＮＣＥ ＳＥＲＶＥＲ ２。１ 呢？
|
| 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
|
