Unable to inhibit ip v6 on mirror zone.
Summary
unable to inhibit ip v6 on mirror zone.
BIND version used
BIND 9.16.0 (Stable Release) <id:6270e602ea>
running on Linux x86_64 5.0.0-38-generic #41-Ubuntu SMP Tue Dec 3 00:27:35 UTC 2019
built by make with '--enable-fixed-rrset' '--enable-dnstap' '--enable-querytrace' '--with-openssl' '--enable-threads' '--with-libxml2' '--with-libjson'
compiled by GCC 8.3.0
compiled with OpenSSL version: OpenSSL 1.1.1b 26 Feb 2019
linked to OpenSSL version: OpenSSL 1.1.1b 26 Feb 2019
compiled with libxml2 version: 2.9.4
linked to libxml2 version: 20904
compiled with json-c version: 0.12.1
linked to json-c version: 0.12.1
compiled with zlib version: 1.2.11
linked to zlib version: 1.2.11
compiled with protobuf-c version: 1.3.2
linked to protobuf-c version: 1.3.2
threads support is enabled
default paths:
named configuration: /usr/local/etc/named.conf
rndc configuration: /usr/local/etc/rndc.conf
DNSSEC root key: /usr/local/etc/bind.keys
nsupdate session key: /usr/local/var/run/named/session.key
named PID file: /usr/local/var/run/named/named.pid
named lock file: /usr/local/var/run/named/named.lock
Steps to reproduce
Add a mirror zone with NS records that resolve to AAAA records
What is the current bug behavior?
(What actually happens.)
09-Mar-2020 12:29:46.434 general: info: zone ./IN: refresh: failure trying master 2620:0:2830:202::132#53 (source ::#0): operation canceled
09-Mar-2020 12:29:46.434 general: info: zone ./IN: refresh: failure trying master 2620:0:2d0:202::132#53 (source ::#0): operation canceled
09-Mar-2020 12:57:54.624 general: info: zone ./IN: refresh: failure trying master 2001:500:84::b#53 (source ::#0): operation canceled
09-Mar-2020 12:57:55.124 general: info: zone ./IN: refresh: failure trying master 2001:500:2f::f#53 (source ::#0): operation canceled
09-Mar-2020 12:57:55.124 general: info: zone ./IN: refresh: failure trying master 2001:7fd::1#53 (source ::#0): operation canceled
09-Mar-2020 12:57:55.624 general: info: zone ./IN: refresh: failure trying master 2620:0:2830:202::132#53 (source ::#0): operation canceled
09-Mar-2020 12:57:55.624 general: info: zone ./IN: refresh: failure trying master 2620:0:2d0:202::132#53 (source ::#0): operation canceled
09-Mar-2020 13:24:27.815 general: info: zone ./IN: refresh: failure trying master 2001:500:84::b#53 (source ::#0): operation canceled
09-Mar-2020 13:24:28.315 general: info: zone ./IN: refresh: failure trying master 2001:500:2f::f#53 (source ::#0): operation canceled
09-Mar-2020 13:24:28.315 general: info: zone ./IN: refresh: failure trying master 2001:7fd::1#53 (source ::#0): operation canceled
09-Mar-2020 13:24:28.815 general: info: zone ./IN: refresh: failure trying master 2620:0:2830:202::132#53 (source ::#0): operation canceled
09-Mar-2020 13:24:28.815 general: info: zone ./IN: refresh: failure trying master 2620:0:2d0:202::132#53 (source ::#0): operation canceled
09-Mar-2020 13:53:34.012 general: info: zone ./IN: refresh: failure trying master 2001:500:84::b#53 (source ::#0): operation canceled
09-Mar-2020 13:53:34.512 general: info: zone ./IN: refresh: failure trying master 2001:500:2f::f#53 (source ::#0): operation canceled
09-Mar-2020 13:53:34.512 general: info: zone ./IN: refresh: failure trying master 2001:7fd::1#53 (source ::#0): operation canceled
09-Mar-2020 13:53:35.012 general: info: zone ./IN: refresh: failure trying master 2620:0:2830:202::132#53 (source ::#0): operation canceled
09-Mar-2020 13:53:35.012 general: info: zone ./IN: refresh: failure trying master 2620:0:2d0:202::132#53 (source ::#0): operation canceled
What is the expected correct behavior?
bind should not be trying to use ipv6 addresses.
Relevant configuration files
server ::/0 { bogus yes; };
listen-on-v6 { none; };
zone "." {.
type mirror;
file "s/db.root";
};