BIND 9.4.3-P2 doesn't delegate zone!
Яцко Эллад Геннадьевич
eyatsko at ngs.ru
Sat Apr 2 10:44:12 UTC 2011
Please, help! What could it be?
172.16.77.1 must delegate zone domain.united-networks.ru
to srvmain.domain.united-networks.ru (W2K3 DC)
But it doesn't! How can it be done?
~~~~~~~~~~~~~~~~~~~~~~~~~~named.conf~~~~~~~~~~~~~~~~~~~~~~~~~~
// $FreeBSD: src/etc/namedb/named.conf,v 1.21.2.1
2005/09/10 08:27:27 dougb Exp $
//
// Refer to the named.conf(5) and named(8) man pages, and
the documentation
// in /usr/share/doc/bind9 for more details.
//
// If you are going to set up an authoritative server,
make sure you
// understand the hairy details of how DNS works. Even
with
// simple mistakes, you can break connectivity for
affected parties,
// or cause huge amounts of useless Internet traffic.
options {
directory "/etc/namedb";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats";
listen-on {
77.37.244.22;
85.21.249.124;
127.0.0.1;
172.16.77.1;
172.17.77.1;
172.31.0.1;
192.168.0.1;
};
forwarders {
77.37.251.33;
85.21.192.3;
};
// query-source address * port 953;
recursion yes;
allow-recursion {0/0;};
};
logging {
channel "default" {
file "/var/log/named.log" versions 2 size
50m;
print-time yes;
print-category yes;
severity debug 90;
};
};
view internal {
match-clients {
127.0.0.1;
127.0.0.0/8;
172.16.0.0/12;
};
zone "0.0.127.in-addr.arpa" {
type master;
file "master/0.0.127.in-addr.arpa";
};
zone "united-networks.ru" {
type master;
file
"master/united-networks.ru.internal";
allow-transfer {
172.16.77.2;
172.18.77.2;
172.31.19.1;
172.31.54.2;
172.31.99.1;
};
};
zone "yatsko.org" {
type master;
file "master/yatsko.org.internal";
allow-transfer {
172.16.77.2;
172.18.77.2;
172.31.19.1;
172.31.54.2;
};
};
zone "runoguy.ru" {
type master;
file "master/runoguy.ru.internal";
allow-transfer {
172.16.77.2;
172.18.77.2;
172.31.19.1;
172.31.54.2;
};
};
zone "domain.runoguy.ru" {
type slave;
masters {
172.16.77.2;
};
file "slave/domain.runoguy.ru.internal";
};
zone "77.16.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/77.16.172.in-addr.arpa";
};
zone "77.17.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/77.17.172.in-addr.arpa";
};
zone "19.16.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/19.16.172.in-addr.arpa";
};
zone "19.17.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/19.17.172.in-addr.arpa";
};
zone "54.18.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/54.18.172.in-addr.arpa";
};
zone "54.19.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/54.19.172.in-addr.arpa";
};
zone "31.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/31.172.in-addr.arpa";
};
zone "77.18.172.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/77.18.172.in-addr.arpa";
};
zone "." {
type hint;
file "named.root";
};
};
view ispnet {
match-clients {
192.168.0.0/24;
};
zone "united-networks.ru" {
type master;
file "master/united-networks.ru.ispnet";
};
zone "runoguy.ru" {
type master;
file "master/runoguy.ru.ispnet";
};
zone "0.168.192.in-addr.arpa" {
type slave;
masters {
172.16.77.2;
};
file "slave/0.168.192.in-addr.arpa";
};
zone "." {
type hint;
file "named.root";
};
};
view external {
match-clients {
any;
};
zone "united-networks.ru" {
type master;
allow-transfer {
80.251.131.2;
};
file
"master/united-networks.ru.external";
};
zone "yatsko.org" {
type master;
allow-transfer {
80.251.131.2;
};
file "master/yatsko.org.external";
};
zone "runoguy.ru" {
type master;
allow-transfer {
80.251.131.2;
80.251.128.148;
};
file "master/runoguy.ru.external";
};
zone "netmyers.net" {
type slave;
masters {
172.31.99.1;
};
file "slave/netmyers.net.external";
};
};
/etc/namedb/master>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~zone:unted-networks.ru.internal~~~~~~~~~~~~~
$TTL 3600
@ IN SOA ns1.united-networks.ru.
root.united-networks.ru. (
2011040210 ; Serial
900 ; Refresh
600 ; Retry
86400 ; Expire
3600 ) ; Minimum
IN NS
ns1.united-networks.ru.
IN MX 10 mx
IN A 172.16.77.1
$ORIGIN domain.united-networks.ru.
IN NS srvmain
IN A 172.16.77.2
srvmain IN A 172.16.77.2
$ORIGIN united-networks.ru.
ns1 IN A 172.16.77.1
mx IN A 172.16.77.1
c2960 IN A 172.16.77.21
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I tried to nslookup from 172.16.77.11:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Server: srvgate-msk.runoguy.ru
Address: 172.16.77.1
*** srvgate-msk.runoguy.ru could not find
wifi.domain.united-networks.ru.: Non
-existent domain
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
And I don't see that the server 172.16.77.1 to queries
172.16.77.2 or returns 172.16.77.2 in its responses.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/root> tshark -ni vlan10 -R dns
Capturing on vlan10
2.841379 172.16.77.11 -> 172.16.77.1 DNS Standard
query PTR 1.77.16.172.in-addr.arpa
2.842683 172.16.77.1 -> 172.16.77.11 DNS Standard
query response PTR srvgate-msk.runoguy.ru
2.853580 172.16.77.11 -> 172.16.77.1 DNS Standard
query A wifi.domain.united-networks.ru
2.854148 172.16.77.1 -> 172.16.77.11 DNS Standard
query response, No such name
2.855307 172.16.77.11 -> 172.16.77.1 DNS Standard
query AAAA wifi.domain.united-networks.ru
2.855894 172.16.77.1 -> 172.16.77.11 DNS Standard
query response, No such name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
More information about the bind-users
mailing list