forum.lissyara.su

Код: Выделить всё

/home/schmel/#cat /etc/rc.conf | grep named
named_enable="YES"

Код: Выделить всё

/home/schmel/#sockstat | grep 53
polw     perl5.10.1 1043  3  udp4   192.168.2.232:13567   192.168.2.232:53
root     authdaemon 953   5  stream /var/run/authdaemond/socket.tmp
bind     named      659   20 tcp4   127.0.0.1:53          *:*
bind     named      659   21 tcp4   127.0.0.1:953         *:*
bind     named      659   22 tcp6   ::1:953               *:*
bind     named      659   512 udp4  127.0.0.1:53          *:*

Код: Выделить всё

/home/schmel/#ps -ax | grep named
  591  ??  Ss     0:00,10 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/r
  659  ??  Is     0:00,20 /usr/sbin/named -t /var/named -u bind
 1211   0  R+     0:00,00 grep named

Код: Выделить всё

/home/schmel/#cat /etc/resolv.conf
domain bizpnz.ru
nameserver      192.168.2.232
nameserver      8.8.8.8

Код: Выделить всё

/home/schmel/#nslookup 2ip.ru
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   2ip.ru
Address: 188.40.74.10
Name:   2ip.ru
Address: 188.40.74.9

Код: Выделить всё

zone "bizpnz.ru" {
        type    master;
        file    "/etc/namedb/master/bizpnz.ru.db";
        notify  YES;
};

Код: Выделить всё

$TTL 12H
$ORIGIN bizpnz.ru.
@               IN              SOA             ns1.bizpnz.ru. postmaster.bizpnz.ru. (
; dmn [bizpnz.ru] timestamp entry BEGIN.
                2010051800     ; Serial
; dmn [bizpnz.ru] timestamp entry END.
                8H              ; Refresh
                15M             ; Retry
                4W              ; Expire
                3H              ; Minimum TTL
)
                IN              NS              ns1.bizpnz.ru.
                IN              NS              ns2.bizpnz.ru.
                IN              MX      10      mail.bizpnz.ru.

bizpnz.ru.     IN              A               192.168.2.232
www             IN              A               192.168.2.232
bizpnz.ru.     IN              TXT             "v=spf1 a mx ip4:192.168.2.232 ip4:192.168.2.232 ~all"
localhost       IN              A               127.0.0.1
mail            IN              A               192.168.2.232
ns1             IN              A               192.168.2.232
ns2             IN              A               85.234.37.66
; CNAME for mail transfer
imap            IN              CNAME           mail
pop             IN              CNAME           mail
pop3            IN              CNAME           mail
relay           IN              CNAME           mail
smtp            IN              CNAME           mail
; CNAME for web transfer
ftp             IN              CNAME           www
; sub [{SUB_NAME}] entry BEGIN.
; sub [{SUB_NAME}] entry END.

Код: Выделить всё

// $FreeBSD: src/etc/namedb/named.conf,v 1.29.2.1.2.1 2009/10/25 01:10:29 kensmith 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 {
        // Relative to the chroot directory, if any
        directory       "/etc/namedb";
        pid-file        "/var/run/named/pid";
        dump-file       "/var/dump/named_dump.db";
        statistics-file "/var/stats/named.stats";

// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
        listen-on       { 127.0.0.1; 85.234.38.81; };

// If you have IPv6 enabled on this system, uncomment this option for
// use as a local resolver.  To give access to the network, specify
// an IPv6 address, or the keyword "any".
//      listen-on-v6    { ::1; };

// These zones are already covered by the empty zones listed below.
// If you remove the related empty zones below, comment these lines out.
        disable-empty-zone "255.255.255.255.IN-ADDR.ARPA";
        disable-empty-zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
        disable-empty-zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below.  This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
        forwarders {
                127.0.0.1;
        };
*/

// If the 'forwarders' clause is not empty the default is to 'forward first'
// which will fall back to sending a query from your local server if the name
// servers in 'forwarders' do not have the answer.  Alternatively you can
// force your name server to never initiate queries of its own by enabling the
// following line:
//      forward only;

// If you wish to have forwarding configured automatically based on
// the entries in /etc/resolv.conf, uncomment the following line and
// set named_auto_forward=yes in /etc/rc.conf.  You can also enable
// named_auto_forward_only (the effect of which is described above).
//      include "/etc/namedb/auto_forward.conf";

        /*
           Modern versions of BIND use a random UDP port for each outgoing
           query by default in order to dramatically reduce the possibility
           of cache poisoning.  All users are strongly encouraged to utilize
           this feature, and to configure their firewalls to accommodate it.

           AS A LAST RESORT in order to get around a restrictive firewall
           policy you can try enabling the option below.  Use of this option
           will significantly reduce your ability to withstand cache poisoning
           attacks, and should be avoided if at all possible.

           Replace NNNNN in the example with a number between 49160 and 65530.
        */
        // query-source address * port NNNNN;
};

// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

// The traditional root hints mechanism. Use this, OR the slave zones below.
zone "." { type hint; file "named.root"; };

/*      Slaving the following zones from the root name servers has some
        significant advantages:
        1. Faster local resolution for your users
        2. No spurious traffic will be sent from your network to the roots
        3. Greater resilience to any potential root server failure/DDoS

        On the other hand, this method requires more monitoring than the
        hints file to be sure that an unexpected failure mode has not
        incapacitated your server.  Name servers that are serving a lot
        of clients will benefit more from this approach than individual
        hosts.  Use with caution.

        To use this mechanism, uncomment the entries below, and comment
        the hint zone above.
*/
/*
zone "." {
        type slave;
        file "slave/root.slave";
        masters {
                192.5.5.241;    // F.ROOT-SERVERS.NET.
        };
        notify no;
};
zone "arpa" {
        type slave;
        file "slave/arpa.slave";
        masters {
                192.5.5.241;    // F.ROOT-SERVERS.NET.
        };
        notify no;
};
zone "in-addr.arpa" {
        type slave;
        file "slave/in-addr.arpa.slave";
        masters {
                192.5.5.241;    // F.ROOT-SERVERS.NET.
        };

        notify no;
};
*/

/*      Serving the following zones locally will prevent any queries
        for these zones leaving your network and going to the root
        name servers.  This has two significant advantages:
        1. Faster local resolution for your users
        2. No spurious traffic will be sent from your network to the roots
*/
// RFC 1912
zone "localhost"        { type master; file "master/localhost-forward.db"; };
zone "127.in-addr.arpa" { type master; file "master/localhost-reverse.db"; };
zone "255.in-addr.arpa" { type master; file "master/empty.db"; };

// RFC 1912-style zone for IPv6 localhost address
zone "0.ip6.arpa"       { type master; file "master/localhost-reverse.db"; };

// "This" Network (RFCs 1912 and 3330)
zone "0.in-addr.arpa"           { type master; file "master/empty.db"; };

// Private Use Networks (RFC 1918)
zone "10.in-addr.arpa"          { type master; file "master/empty.db"; };
zone "16.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "17.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "18.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "19.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "20.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "21.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "22.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "23.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "24.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "25.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "26.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "27.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "28.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "29.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "30.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "31.172.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "168.192.in-addr.arpa"     { type master; file "master/empty.db"; };

// Link-local/APIPA (RFCs 3330 and 3927)
zone "254.169.in-addr.arpa"     { type master; file "master/empty.db"; };

// TEST-NET for Documentation (RFC 3330)
zone "2.0.192.in-addr.arpa"     { type master; file "master/empty.db"; };

// Router Benchmark Testing (RFC 3330)
zone "18.198.in-addr.arpa"      { type master; file "master/empty.db"; };
zone "19.198.in-addr.arpa"      { type master; file "master/empty.db"; };

// IANA Reserved - Old Class E Space
zone "240.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "241.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "242.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "243.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "244.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "245.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "246.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "247.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "248.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "249.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "250.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "251.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "252.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "253.in-addr.arpa"         { type master; file "master/empty.db"; };
zone "254.in-addr.arpa"         { type master; file "master/empty.db"; };

// IPv6 Unassigned Addresses (RFC 4291)
zone "1.ip6.arpa"               { type master; file "master/empty.db"; };
zone "3.ip6.arpa"               { type master; file "master/empty.db"; };
zone "4.ip6.arpa"               { type master; file "master/empty.db"; };
zone "5.ip6.arpa"               { type master; file "master/empty.db"; };
zone "6.ip6.arpa"               { type master; file "master/empty.db"; };
zone "7.ip6.arpa"               { type master; file "master/empty.db"; };
zone "8.ip6.arpa"               { type master; file "master/empty.db"; };
zone "9.ip6.arpa"               { type master; file "master/empty.db"; };
zone "a.ip6.arpa"               { type master; file "master/empty.db"; };
zone "a.ip6.arpa"               { type master; file "master/empty.db"; };
zone "b.ip6.arpa"               { type master; file "master/empty.db"; };
zone "c.ip6.arpa"               { type master; file "master/empty.db"; };
zone "d.ip6.arpa"               { type master; file "master/empty.db"; };
zone "e.ip6.arpa"               { type master; file "master/empty.db"; };
zone "0.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "1.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "2.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "3.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "4.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "5.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "6.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "7.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "8.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "9.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "a.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "b.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "0.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "1.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "2.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "3.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "4.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "5.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "6.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "7.e.f.ip6.arpa"           { type master; file "master/empty.db"; };

// IPv6 ULA (RFC 4193)
zone "c.f.ip6.arpa"             { type master; file "master/empty.db"; };
zone "d.f.ip6.arpa"             { type master; file "master/empty.db"; };

// IPv6 Link Local (RFC 4291)
zone "8.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "9.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "a.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "b.e.f.ip6.arpa"           { type master; file "master/empty.db"; };

// IPv6 Deprecated Site-Local Addresses (RFC 3879)
zone "c.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "d.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "e.e.f.ip6.arpa"           { type master; file "master/empty.db"; };
zone "f.e.f.ip6.arpa"           { type master; file "master/empty.db"; };

// IP6.INT is Deprecated (RFC 4159)
zone "ip6.int"                  { type master; file "master/empty.db"; };

// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example slave zone config entries.  It can be convenient to become
// a slave at least for the zone your own domain is in.  Ask
// your network administrator for the IP address of the responsible
// master name server.
//
// Do not forget to include the reverse lookup zone!
// This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended, or ".IP6.ARPA" for IPv6.
//
// Before starting to set up a master zone, make sure you fully
// understand how DNS and BIND work.  There are sometimes
// non-obvious pitfalls.  Setting up a slave zone is usually simpler.
//
// NB: Don't blindly enable the examples below. :-)  Use actual names
// and addresses instead.

/* An example dynamic zone
key "exampleorgkey" {
        algorithm hmac-md5;
        secret "sf87HJqjkqh8ac87a02lla==";
};
zone "example.org" {
        type master;
        allow-update {
                key "exampleorgkey";
        };
        file "dynamic/example.org";
};
*/

/* Example of a slave reverse zone
zone "2.168.192.in-addr.arpa" {
        type slave;
        file "slave/2.168.192.in-addr.arpa";
        masters {
                192.168.2.232;
        };
};
*/


// bind Data BEGIN.

// dmn [bizpnz.ru] cfg entry BEGIN.
zone "bizpnz.ru" {
        type    master;
        file    "/etc/namedb/master/bizpnz.ru.db";
        notify  YES;
};
zone "admin.bizpnz.ru" {
        type    master;
        file    "/etc/namedb/master/admin.bizpnz.ru.db";
        notify  YES;
};

// bind Data END.

Код: Выделить всё

C:\Documents and Settings\user>nslookup admin.bizpnz.ru
*** Can't find server name for address 85.234.38.56: Query refused
Server:  net144.144.91-3.espenza.ru
Address:  91.144.144.3

*** net144.144.91-3.espenza.ru can't find admin.bizpnz.ru: Non-existent domain

Код: Выделить всё

*** Can't find server name for address 85.234.38.81: Query refused

Код: Выделить всё

nslookup - ИПадресПоКоторомуПланируетсяБытьВиднымПримариДНСсерверу

Код: Выделить всё

[schmel@hosting:~] $nslookup bizpnz.ru
Server:         192.168.2.232
Address:        192.168.2.232#53

Name:   bizpnz.ru
Address: 192.168.2.232

Код: Выделить всё

        listen-on       { 127.0.0.1; 192.168.2.232; 85.234.38.81; };

Код: Выделить всё

C:\Documents and Settings\user>nslookup mail.ru
[b]*** Can't find server name for address 85.234.38.56: Query refused[/b]
Server:  net144.144.91-3.espenza.ru
Address:  91.144.144.3

Non-authoritative answer:
Name:    mail.ru
Addresses:  217.69.128.41, 217.69.128.42, 217.69.128.43, 217.69.128.44
          217.69.128.45

Код: Выделить всё

C:\Documents and Settings\schmel>nslookup mail.ru
*** Can't find server name for address 192.168.2.232: Non-existent domain
Server:  pool-192.168.2.254.local
Address:  192.168.2.254

Non-authoritative answer:
Name:    mail.ru
Addresses:  217.69.128.41, 217.69.128.42, 217.69.128.43, 217.69.128.44
          217.69.128.45

Код: Выделить всё

#sockstat | grep 53
bind     named      1660  20 tcp4   192.168.2.232:53      *:*
bind     named      1660  21 tcp4   127.0.0.1:53          *:*
bind     named      1660  22 tcp4   127.0.0.1:953         *:*
bind     named      1660  23 tcp6   ::1:953               *:*
bind     named      1660  512 udp4  192.168.2.232:53      *:*
bind     named      1660  513 udp4  127.0.0.1:53          *:*
[b]polw     perl5.10.1 1207  3  udp4   192.168.2.232:55804   192.168.2.232:53
polw     perl5.10.1 1043  3  udp4   192.168.2.232:43905   192.168.2.232:53[/b]
root     authdaemon 953   5  stream /var/run/authdaemond/socket.tmp

Код: Выделить всё

C:\Documents and Settings\Администратор>nslookup mail.ru
*** Can't find server name for address 192.168.2.232: Server failed
Server:  UnKnown
Address:  192.168.2.232

Non-authoritative answer:
Name:    mail.ru
Addresses:  217.69.128.42, 217.69.128.43, 217.69.128.44, 217.69.128.45
          217.69.128.41

Код: Выделить всё

//  reverse zone
zone "2.168.192.in-addr.arpa" {
        type master;
        file "/etc/namedb/master/2.168.192.in-addr.arpa";
};

Код: Выделить всё

$TTL 12H
$ORIGIN         2.168.192.in-addr.arpa.

@               IN              SOA             ns1.bizpnz.ru. (
; dmn [bizpnz.ru] timestamp entry BEGIN.
                2010051800     ; Serial
; dmn [bizpnz.ru] timestamp entry END.
                8H              ; Refresh
                15M             ; Retry
                4W              ; Expire
                3H              ; Minimum TTL
)
                IN              NS              ns1.bizpnz.ru.

bizpnz.ru.      IN              A               192.168.2.232
www             IN              A               192.168.2.232
localhost       IN              A               127.0.0.1
mail            IN              A               192.168.2.232
ns1             IN              A               192.168.2.232
; CNAME for web transfer
ftp             IN              CNAME           www


232             IN      PTR     bizpnz.ru. 
234             IN      PTR     jabber.bizpnz.ru.

Код: Выделить всё

$TTL 12H
$ORIGIN         2.168.192.in-addr.arpa.

@               IN              SOA             ns1.bizpnz.ru. (
; dmn [bizpnz.ru] timestamp entry BEGIN.
                2010051800     ; Serial
; dmn [bizpnz.ru] timestamp entry END.
                8H              ; Refresh
                15M             ; Retry
                4W              ; Expire
                3H              ; Minimum TTL
)
                IN              NS              ns1.bizpnz.ru.
232                            PTR            ns1.bizpnz.ru.

Код: Выделить всё

/*
        forwarders {
                127.0.0.1;
        };
*/

Код: Выделить всё

C:\Documents and Settings\Администратор>nslookup mail.ru
Server:  ns1.bizpnz.ru
Address:  192.168.2.232

Non-authoritative answer:
Name:    mail.ru
Addresses:  217.69.128.43, 217.69.128.44, 217.69.128.45, 217.69.128.41
          217.69.128.42

Код: Выделить всё

$TTL 3h
@ SOA  ns1.bizpnz.ru. ns1.bizpnz.ru. 42 1d 12h 1w 3h
; Serial, Refresh, Retry, Expire, Neg. cache TTL
                NS      ns1.bizpnz.ru.
232   PTR     ns1.bizpnz.ru.
234   PTR     jabber.bizpnz.ru.