Clients端
vi /etc/resolv.conf
nameserver 10.10.1.1
nameserver 10.10.1.2
nameserver 168.95.1.1
nameserver 168.95.192.1
dns查詢,先從/etc/hosts,再從/etc/resolv.conf
vi /etc/nsswitch.conf
hosts: files dns
工具
nslookup ssorc.tw
dig @168.95.1.1 ssorc.tw
dig @168.95.1.1 ssorc.tw MX
dig @168.95.1.1 ssorc.tw NS
[Q1.] cat /var/log/messages
Oct 5 05:02:30 test named[432]: lame server resolving
[A1.] 當DNS主機在向外面的DNS系統查詢某些正反解時,可能由於對方DNS主機的設定錯誤,導致無法解析到預期的正反解結果,這個時候就會發生所謂的 lame server 的錯誤!無嚴重的後果,僅是對方的設定錯誤
vi /etc/named.conf
logging { // 加入這個參數:
category lame-servers { null; };
};// logging 是主要的參數,至於 category 則是定義出什麼資訊,
// 因為我們不要 lame server ,
// 所以選擇 lame-servers 這個參數,並定義參數值為 null
[Q2:] cat /var/log/messages
couldn't add command channel 127.0.0.1#953: not found
[A2:] DNS 系統必須要提供 rndc key,執行,rndc-confgen,產生
# Start of rndc.conf
key "rndckey" {
algorithm hmac-md5;
secret "VumZ9GIx2zafogkWxpzD6A==";
};options {
default-key "rndckey";
default-server 127.0.0.1;
default-port 953;
};
# End of rndc.conf# Use with the following in named.conf, adjusting the allow list as needed:
# key "rndckey" {
# algorithm hmac-md5;
# secret "VumZ9GIx2zafogkWxpzD6A==";
# };
#
# controls {
# inet 127.0.0.1 port 953
# allow { 127.0.0.1; } keys { "rndckey"; };
# };
# End of named.conf
將上面複製到 /etc/rndc.conf,並且 vi /etc/named.conf
key "rndckey" {
algorithm hmac-md5;
secret "VumZ9GIx2zafogkWxpzD6A==";
};controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndckey"; };
};
附註
fedora core 4的 RPM的設定
cat /etc/rndc.key
key "rndckey" {
algorithm hmac-md5;
secret "V86aF6ZOo7l7MUn2E5VqtlXC9x3kdoifFrYyEU8DVE9xiRlzu1Vt4Gd2N2VA";
};
cat /etc/rndc.conf
options {
default-server localhost;
default-key "rndckey";
};server localhost {
key "rndckey";
};include "/etc/rndc.key";
[Q1.] 當查詢domain name時,字串出現了non-authoritative answer,
[A1.] 此意思是從local dns的cache找出來的,非從外面的name server找出。
線上查詢工具
[Q2] zone ssorc.tw/IN: journal rollforward failed: journal out of sync with zone
[A2] 刪除 zone.ssorc.tw.jnl檔
留言