Я настраиваю файл зоны для обратного просмотра зоны, в настоящее время я получаю эту ошибку: зона L00012345.ie/IN: загрузка из основного файла 102.168.192.db завершилась неудачно: файл не найден

Не удалось найти причину ошибки. В целях тестирования у меня есть только 1 DNS-сервер с IP-адресом 192.168.102.10, указанные ниже файлы настроены на том же DNS-сервере 192.168.102.10.

файл named.conf

//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// See the BIND Administrator's Reference Manual (ARM) for details about the
// configuration located in /usr/share/doc/bind-{version}/Bv9ARM.html

acl internals { 192.168.102.0/24; };

options {
        listen-on port 53 { 127.0.0.1;192.168.102.10; };
        listen-on-v6 port 53 { ::1; };
        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_mem_stats.txt";
        recursing-file "/var/named/data/named.recursing";
        secroots-file "/var/named/data/named.secroots";
        allow-query   { localhost; internals; };

        /*
        - If you are building an AUTHORITATIVE DNS server, do NOT enable recursion.
        - If you are building a RECURSIVE (caching) DNS server, you need to enable
          recursion.
        - If your recursive DNS server has a public IP address, you MUST enable access
          control to limit queries to your legitimate users. Failing to do so will
          cause your server to become part of large scale DNS amplification
          attacks. Implementing BCP38 within your network would greatly
          reduce such attack surface
        */
        recursion yes;

        dnssec-enable yes;
        dnssec-validation yes;

        /* Path to ISC DLV key */
        bindkeys-file "/etc/named.iscdlv.key";

        managed-keys-directory "/var/named/dynamic";

        pid-file "/run/named/named.pid";
        session-keyfile "/run/named/session.key";
};

logging {
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

zone "." IN {
        type hint;
        file "named.ca";
};

zone "L00012345.ie" { type master; file "L00012345.db"; };

zone "102.168.192.IN-ADDR.ARPA" { type master; file "102.168.192.db"; };

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

Файл L00012345.db

$TTL 3H
$ORIGIN L00012345.ie.

@     IN SOA ns1.L00012345.ie. admin.L00012345.ie. (
                                        0     ; serial
                                        1D     ; refresh
                                        1H     ; retry
                                        1W     ; expire
                                        3H )   ; minimum
        IN NS L00012354.ie.

ns1   IN A 192.168.102.149

Файл 102.168.192.db

$TTL 3H
$ORIGIN 102.168.192.IN-ADDR.ARPA.

@     IN SOA ns1.L00012345.ie. admin.L00012345.ie. (
                                        0     ; serial
                                        1D     ; refresh
                                        1H     ; retry
                                        1W     ; expire
                                        3H )   ; minimum
        IN NS L00012354.ie.

10   IN PTR L00012345.ie.

Благодарю вас

|источник

0