☰

为命名创建多个日志流

tag-icon • tag-icon logging bind named-conf
为命名创建多个日志流

我正在推出外部 DNS 服务器来解析所有最终用户查询

在我们将解决方案投入生产之前，我希望尽可能多地提供有用的日志记录

这是 named.conf 文件（称为命名空间的 gi-named.conf 文件）

options {
        listen-on port 53 { Public IP; };
        #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     { any; };
        allow-query-on  { PublicIP; };

        /*
         - 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;
        allow-query-cache { Internal Range; };
        allow-query-cache-on  { PublicIP; };



        query-source address Public IP ;

        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
{
/*      If you want to enable debugging, eg. using the 'rndc trace' command,
 *      named will try to write the 'named.run' file in the $directory (/var/named).
 *      By default, SELinux policy does not allow named to modify the /var/named directory,
 *      so put the default debug log file in data/ :
 */
        /*channel default_debug {
                print-time yes;
                print-category yes;
                print-severity yes;
                file "data/named.run";
                severity dynamic;
        };*/
        channel queries_log {
                file "/var/log/queries" versions 1 size 20m;
                print-time yes;
                print-category yes;
                print-severity yes;
                severity debug 3;
        };
        channel default_log {
           file "/var/named/log/default" versions 3 size 20m;
           print-time yes;
           print-category yes;
           print-severity yes;
           severity info;
    };
       channel query-errors_log {
           file "/var/named/log/query-errors" versions 5 size 20m;
           print-time yes;
           print-category yes;
           print-severity yes;
           severity dynamic;
    };

        category queries { queries_log; };
        category client { queries_log;  };
};

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

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

我遇到的问题是，虽然我看到日志填充 /var/named/log/queries 文件，但我在 /var/named/log/query-error 日志文件或 /var/named/log/default 日志文件中都看不到任何日志，而且我不确定我到底错在哪里，或者我是否遗漏了一些配置

有人曾经经历过这种情况吗？

答案1

因此，问题似乎在于我尝试创建的日志文件和日志通道在我使用的绑定版本中不可用。

我运行了 yum update bind-utils，它让我更新到 9.11 版本。

自更新以来，所有日志通道均正常运行

相关内容