solaris dns配置
昨晚尝试了一下solaris dns搭建，有必要记录下来～备看
vi /etc/named.conf ,新建正向域baidu.com
options{
directory “/var/named”; //文件目录
forward first;
forwarders {
218.85.157.99; //设置转发器IP
211.97.104.129;
202.101.98.54;
202.102.98.55;
};
listen-on { 127.0.0.1; 210.34.80.3; }
listen-on-v6 { any; };
};
#key “rndc-key”{
# algorithm hmac-md5;
# secret “+AkMVc1T+DaZoUQSX1RZsQ==”;
#};
controls{
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { “rndc-key
};
zone “.”{
type hint;
file “named.root”;
};
zone “localhost” IN {
type master;
file “localhost.zone”;
allow-update { none; };
};
zone “0.0.127.in-addr.arpa”{
type master;
file “localhost.reverse”;
allow-update { none; };
notify no;
};
zone “baidu.com”{
type master;
file “baidu.com.hosts”; //关联文件名
allow-update { none; };
/var/named ,建立 baidu.com.hosts
$ORIGIN .
$TTL 10800
baidu.com IN SOA e3000.fjau.edu.cn. root.fjau.edu.cn.(
2009032010
3600
900
64800
10800
)
NS dns1.baidu.com //ns 很重要。一定要填写
NS dns2.baidu.com
$ORIGIN baidu.com.
www A 121.14.88.14
zhidao A 220.181.43.128
-bash-3.00# /usr/sbin/named -g //这条命令很重要，可以查看DNS服务运行信息
Apr 23 14:44:02.832 starting BIND 9.2.4 -g
Apr 23 14:44:02.832 using 4 CPUs
Apr 23 14:44:02.835 loading configuration from ‘/etc/named.conf’
Apr 23 14:44:02.836 listening on IPv6 interfaces, port 53
Apr 23 14:44:02.836 binding TCP socket: address in use
Apr 23 14:44:02.837 listening on IPv4 interface lo0:3, 127.0.0.1#53
Apr 23 14:44:02.837 binding TCP socket: address in use
Apr 23 14:44:02.837 listening on IPv4 interface e1000g0:6, 210.34.80.3#53
Apr 23 14:44:02.837 binding TCP socket: address in use
Apr 23 14:44:02.840 /etc/named.conf:21: couldn’t add command channel 127.0.0.1#9
53: address in use
Apr 23 14:44:02.840 ignoring config file logging statement due to -g option
Apr 23 14:44:02.841 zone 0.0.127.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.843 zone 80.34.210.in-addr.arpa/IN: loaded serial 2008051606
Apr 23 14:44:02.843 zone 81.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.843 zone 83.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.843 zone 84.34.210.in-addr.arpa/IN: loaded serial 2007041901
Apr 23 14:44:02.843 zone 85.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.844 zone 86.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.844 zone 87.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.844 zone 88.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.844 zone 89.34.210.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.844 zone 3.5.218.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.845 zone 255.79.59.in-addr.arpa/IN: loaded serial 4
Apr 23 14:44:02.846 zone baidu.com/IN: loaded serial 2009031010
Apr 23 14:44:02.847 zone 0.0.0.b.0.0.8.e.8.a.d.0.1.0.0.2.ip6.int/IN: loaded seri
al 4
Apr 23 14:44:02.847 zone localhost/IN: loaded serial 4
Apr 23 14:44:02.847 running
Apr 23 14:44:02.847 zone 84.34.210.in-addr.arpa/IN: sending notifies (serial 200
7041901)
Apr 23 14:44:02.847 zone 88.34.210.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.847 zone localhost/IN: sending notifies (serial 4)
Apr 23 14:44:02.847 zone 86.34.210.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.847 zone baidu.com/IN: sending notifies (serial 2009031010)
Apr 23 14:44:02.847 zone 0.0.0.b.0.0.8.e.8.a.d.0.1.0.0.2.ip6.int/IN: sending not
ifies (serial 4)
Apr 23 14:44:02.847 zone 81.34.210.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.847 zone 87.34.210.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.847 zone 85.34.210.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.848 zone 255.79.59.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.848 zone 89.34.210.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.848 zone 3.5.218.in-addr.arpa/IN: sending notifies (serial 4)
Apr 23 14:44:02.848 zone 83.34.210.in-addr.arpa/IN: sending notifies (serial 4)
^CApr 23 14:44:18.995 shutting down
Apr 23 14:44:18.996 no longer listening on ::#53
Apr 23 14:44:18.996 no longer listening on 127.0.0.1#53
Apr 23 14:44:18.996 no longer listening on 210.34.80.3#53
Apr 23 14:44:18.999 exiting
