GitLab

Summary

'rndc reload' causes an assertion failure when "168.192.in-addr.arpa" slave zone (which fails to transfer because the master doesn't have it) is removed from named.conf

Steps to reproduce

1. Install bind-9.9.4-61.el7_5.1.x86_64

2. Start named using "named.conf" shown below

3. Remove the "168.192.in-addr.arpa" zone from named.conf

4. rndc reload

What is the current bug behavior?

named crashes with the message below

What is the expected correct behavior?

'rndc reload' completes successfully, named loads the new config

Relevant configuration files

options {
    listen-on port 53 { any; };
    listen-on-v6 port 53 { none; };
    forwarders { 1.1.1.1; 8.8.8.8; };
    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";
    allow-query { any; };
    allow-query-cache { any; };
    recursion yes;
    allow-recursion { any; };

    dnssec-enable false;
    dnssec-validation false;
    dnssec-lookaside auto;

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

logging {
    channel main_log {
        file "/var/log/named/named.log" versions 3 size 5m;
        severity info;
        print-time yes;
        print-severity yes;
        print-category yes;
    };
    category default{
        main_log;
    };
    category lame-servers {
        null;
    };
};

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

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

zone "168.192.in-addr.arpa" IN { type slave; masters { 192.168.1.1; }; file "slaves/168.192.in-addr.arpa.db"; };

Relevant logs and/or screenshots

28-Aug-2018 13:54:23.481 general: critical: zone.c:4586: REQUIRE(prev > 0) failed, back trace
28-Aug-2018 13:54:23.481 general: critical: #0 0x7f796dec0b60 in ??
28-Aug-2018 13:54:23.481 general: critical: #1 0x7f796c02117a in ??
28-Aug-2018 13:54:23.481 general: critical: #2 0x7f796d7d6471 in ??
28-Aug-2018 13:54:23.481 general: critical: #3 0x7f796d7e7a70 in ??
28-Aug-2018 13:54:23.481 general: critical: #4 0x7f796d70e5cd in ??
28-Aug-2018 13:54:23.481 general: critical: #5 0x7f796d70e73b in ??
28-Aug-2018 13:54:23.481 general: critical: #6 0x7f796d7e87da in ??
28-Aug-2018 13:54:23.481 general: critical: #7 0x7f796d7e8892 in ??
28-Aug-2018 13:54:23.481 general: critical: #8 0x7f796d7b6371 in ??
28-Aug-2018 13:54:23.481 general: critical: #9 0x7f796ded96e5 in ??
28-Aug-2018 13:54:23.481 general: critical: #10 0x7f796dedca26 in ??
28-Aug-2018 13:54:23.481 general: critical: #11 0x7f796dedcf18 in ??
28-Aug-2018 13:54:23.481 general: critical: #12 0x7f796deb93e5 in ??
28-Aug-2018 13:54:23.481 general: critical: #13 0x7f796debc197 in ??
28-Aug-2018 13:54:23.481 general: critical: #14 0x7f796c044066 in ??
28-Aug-2018 13:54:23.481 general: critical: #15 0x7f796bbf4dc5 in ??
28-Aug-2018 13:54:23.481 general: critical: #16 0x7f796ac6d73d in ??
28-Aug-2018 13:54:23.481 general: critical: exiting (due to assertion failure)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem.)