Cent OS Zone Files for Reverse Lookup / loading from master file failed












0















I'm setting up zone file for Reverse Zone lookup, currently I am receiving this error : zone L00012345.ie/IN: loading from master file 102.168.192.db failed: file not found



Not able to find where the error is, for testing purpose I only have 1 DNS server with IP 192.168.102.10, the below files are configured on the same 192.168.102.10 DNS server.



named.conf file



//
// 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 file



$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 file



$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.


Thank You










share|improve this question





























    0















    I'm setting up zone file for Reverse Zone lookup, currently I am receiving this error : zone L00012345.ie/IN: loading from master file 102.168.192.db failed: file not found



    Not able to find where the error is, for testing purpose I only have 1 DNS server with IP 192.168.102.10, the below files are configured on the same 192.168.102.10 DNS server.



    named.conf file



    //
    // 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 file



    $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 file



    $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.


    Thank You










    share|improve this question



























      0












      0








      0








      I'm setting up zone file for Reverse Zone lookup, currently I am receiving this error : zone L00012345.ie/IN: loading from master file 102.168.192.db failed: file not found



      Not able to find where the error is, for testing purpose I only have 1 DNS server with IP 192.168.102.10, the below files are configured on the same 192.168.102.10 DNS server.



      named.conf file



      //
      // 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 file



      $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 file



      $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.


      Thank You










      share|improve this question
















      I'm setting up zone file for Reverse Zone lookup, currently I am receiving this error : zone L00012345.ie/IN: loading from master file 102.168.192.db failed: file not found



      Not able to find where the error is, for testing purpose I only have 1 DNS server with IP 192.168.102.10, the below files are configured on the same 192.168.102.10 DNS server.



      named.conf file



      //
      // 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 file



      $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 file



      $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.


      Thank You







      dns






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 27 '18 at 19:07







      Huud Rych

















      asked Dec 27 '18 at 18:40









      Huud RychHuud Rych

      127




      127






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388203%2fcent-os-zone-files-for-reverse-lookup-loading-from-master-file-failed%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388203%2fcent-os-zone-files-for-reverse-lookup-loading-from-master-file-failed%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Plaza Victoria

          Puebla de Zaragoza

          Musa