Уважаемые коллеги, просьба подсказать, как победить следующую ситуацию:[root@ns log]# dig inn.ru
; <<>> DiG 9.3.4-P1 <<>> inn.ru
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 41657
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;inn.ru. IN A
;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Dec 1 09:38:08 2009
;; MSG SIZE rcvd: 24
Но вот если так, то:
[root@ns log]# dig +norec inn.ru
; <<>> DiG 9.3.4-P1 <<>> +norec inn.ru
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24697
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;inn.ru. IN A
;; AUTHORITY SECTION:
inn.ru. 345460 IN NS gtm2.inn.ru.
inn.ru. 345460 IN NS gtm1.inn.ru.
;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Dec 1 09:38:31 2009
;; MSG SIZE rcvd: 62
Что тут может быть не так?
Конфиг bind`а:
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named.memstats.txt";
version "no version info";
# query-source port 53;
query-source address XXXXX;
listen-on port 53 { 127.0.0.1; XXXXX; XXXXXX; };
listen-on-v6 { none; };
cleaning-interval 60;
interface-interval 60;
notify yes;
recursion yes;
# zone-statistics yes;
auth-nxdomain yes;
max-transfer-time-in 60;
max-transfer-time-out 60;
max-cache-size 200M;
allow-query { any; };
allow-transfer { "ripn"; "ripe"; "transfer"; };
allow-recursion { "server"; "transfer"; "XXX"; "our_as"; "XXX"; "XXX"; "XXX"; };
blackhole { "bogon"; };
Вариант для распечатки
OpenNET: Виртуальная конференция (Public)
(ok) on 01-Дек-09, 09:42 
