Hi,
Sorry I had to fix for my customer the domain ore.org.bo, but I have
open another domain to test: testadmin.ovh
Sorry for all this change. I have defined better test case and have
normal IP to prevent problem from this part.
69.162.65.138-> not my IP 2803:1920::4:a09 IPv6 only, VPS customer (here I'm the
customer) <-> EDGE 199.38.247.210 IPv4+IPv6 <-> upstream provider of my
autonomous system Each time I try enable log, named not start, see
attached file Debian 12 into /etc/bind/named.conf.local I replace
(/var/log/bind.log exist with bind user): logging { category
default { null; }; }; logging { channel bind_log {
file "/var/log/bind.log" versions 3 size 10m;
severity info; print-category yes;
print-severity yes; print-time yes;
}; category default { bind_log; }; category
lame-servers { null; }; category update { bind_log; };
category update-security { bind_log; }; category security {
bind_log; }; };
alpha_one_x86/BRULE Herman<alpha_one_...@first-world.info>
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server
management
IT, OS, technologies, research & development, security and business department
On 7/15/24 02:43, Mark Andrews wrote:
Really it is very hard to help people who keep changing random things making a
moving
target. You started out with a machine at 45.225.75.8 that could reach
2803:1920::c:1963
based on the forward zone declaration so it had to be dual stacked (both IPv4
and IPv6).
You have now added two new machines 69.162.65.138 and 192.169.93.210 which may
or may not
be able to reach 2803:1920::c:1963 and have changed the delegation to point to
them and they
return NXDOMAIN for smtp.ore.org.bo.
Now if you have IPv4 only nameservers that need to get the zone content from an
IPv6 only
server you will need to have an intermediate dual stacked server that can
transfer the zone
content from the IPv6 only server and send it to the IPv4 only servers when
they request it.
P(IPv6-only) -> I(IPv4 and IPv6) -> S(IPv4 only)
Also read the nameserver’s logs. They will help you work out what is going
wrong.
2803:1920::c:1963 (IPv6 only):
zone ore.org.bo {
type primary;
file "ore.org.bo.db”;
};
45.225.75.8/<ipv6addess> (dual stacked):
zone ore.org.bo {
type secondary;
file "ore.org.bo.db”;
primaries { 2803:1920::c:1963; };
};
69.162.65.138 (IPv4 only):
zone ore.org.bo {
type secondary;
file "ore.org.bo.db”;
primaries { 45.225.75.8; };
};
Alternatively you can add IPv6 to an IPv4 only machine using services like
https://tunnelbroker.net/ even when the ISP does not support IPv6.
Mark
On 15 Jul 2024, at 11:00, Herman Brule<cont...@herman-brule.com> wrote:
I open this to test (45.225.75.8 is particial anycast IP, for DNS/UDP have
bind9):
dig A ore.org.bo @199.38.247.210
With on 199.38.247.210 (work):
zone ore.org.bo {
type master;
file "/etc/bind/ore.org.bo.db";
};
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> A ore.org.bo @199.38.247.210
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39291
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 9948d53f96271fa80100000066947311b2e477062b98c6ee (good)
;; QUESTION SECTION:
;ore.org.bo. IN A
;; ANSWER SECTION:
ore.org.bo. 3600 IN A 45.225.75.8
;; Query time: 99 msec
;; SERVER: 199.38.247.210#53(199.38.247.210) (UDP)
;; WHEN: Mon Jul 15 00:53:38 UTC 2024
;; MSG SIZE rcvd: 83
With on 199.38.247.210 (not work):
zone ore.org.bo {
type secondary;
file “/etc/bind/ore.org.bo.db”;
primaries { 2803:1920::c:1963; };
};
; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> A ore.org.bo @199.38.247.210
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14941
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: f9006eb35715f0da01000000669473a08e2898af7098316c (good)
;; QUESTION SECTION:
;ore.org.bo. IN A
;; Query time: 87 msec
;; SERVER: 199.38.247.210#53(199.38.247.210) (UDP)
;; WHEN: Mon Jul 15 00:56:01 UTC 2024
;; MSG SIZE rcvd: 67
alpha_one_x86/BRULE Herman<alpha_one_...@first-world.info>
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server
management
IT, OS, technologies, research & development, security and business department
On 7/14/24 20:00, Mark Andrews wrote:
On 13 Jul 2024, at 12:44, Herman Brule<cont...@herman-brule.com> wrote:
Thanks, I'm looking how solve this, cleanly.
In my country only 1 ISP have IPv6, then I need keep IPv4.
I have 1 IPv4 for 1000 VPS, no way here to have more IPv4.
Then:
1) I'm not sure if my DNS authoritative on IPv6 reply correctly (but reply
correctly to all my dig query)
2) I have to provide a way to my customer can resolve query on their DNS server
on their IPv6 VPS, their need be able to just put their vps dns or at least
common server dns (where I had to put their zone, then I dislike this idea)
For now your method fail, include I try:
zone "ore.org.bo" {
type master;
file "/etc/bind/ore.org.bo.db";
};
But failed too.
Well I didn’t say to do that. You have they wrong type of zone. Make it a
secondary (slave) zone
like I told you to do.
zone ore.org.bo {
type secondary;
file “ore.org.bo.db”;
primaries { 2803:1920::c:1963; };
};
Now that should work as I can AXFR the zone from that server. You should also
note the difference in
the flags in the responses for smtp.ore.org.bo. The one from 2803:1920::c:1963
is an authoritative
reply (aa) and the TTL stays at 3600, whereas the one from 45.225.75.8 is not
(aa is not set in the
flags) and the TTL decreases indicating that it comes from a recursive server.
It also looks like someone tried to comment out *.ore.org.bo but used the wrong
comment character ‘#'
rather than ‘;’.
[ant:~/git/bind9] marka% dig axfr ore.org.bo @2803:1920::c:1963
; <<>> DiG 9.19.25-dev <<>> axfr ore.org.bo @2803:1920::c:1963
;; global options: +cmd
ore.org.bo. 604800 IN SOA 811.vps.confiared.com. admin.ore.org.bo. 3 604800
86400 2419200 604800
ore.org.bo. 604800 IN NS 811.vps.confiared.com.
ore.org.bo. 3600 IN MX 1 smtp.ore.org.bo.
ore.org.bo. 3600 IN A 45.225.75.8
ore.org.bo. 3600 IN AAAA 2803:1920::c:1963
#*.ore.org.bo. 604800 IN CNAME ore.org.bo.
smtp.ore.org.bo. 3600 IN A 45.225.75.8
smtp.ore.org.bo. 3600 IN AAAA 2803:1920::c:1963
www.ore.org.bo. 604800 IN CNAME ore.org.bo.
ore.org.bo. 604800 IN SOA 811.vps.confiared.com. admin.ore.org.bo. 3 604800
86400 2419200 604800
;; Query time: 497 msec
;; SERVER: 2803:1920::c:1963#53(2803:1920::c:1963) (TCP)
;; WHEN: Mon Jul 15 09:47:16 AEST 2024
;; XFR size: 10 records (messages 1, bytes 324)
[ant:~/git/bind9] marka% dig a smtp.ore.org.bo @2803:1920::c:1963
; <<>> DiG 9.19.25-dev <<>> a smtp.ore.org.bo @2803:1920::c:1963
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4584
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: cdbac4bb692528b301000000669463a2ffd887df1b2535a8 (good)
;; QUESTION SECTION:
;smtp.ore.org.bo. IN A
;; ANSWER SECTION:
smtp.ore.org.bo. 3600 IN A 45.225.75.8
;; Query time: 659 msec
;; SERVER: 2803:1920::c:1963#53(2803:1920::c:1963) (UDP)
;; WHEN: Mon Jul 15 09:47:47 AEST 2024
;; MSG SIZE rcvd: 88
[ant:~/git/bind9] marka% dig a smtp.ore.org.bo @45.225.75.8
; <<>> DiG 9.19.25-dev <<>> a smtp.ore.org.bo @45.225.75.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33189
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 42c6758d745eb62b01000000669463baea9db7cd3474c256 (good)
;; QUESTION SECTION:
;smtp.ore.org.bo. IN A
;; ANSWER SECTION:
smtp.ore.org.bo. 3266 IN A 45.225.75.8
;; Query time: 264 msec
;; SERVER: 45.225.75.8#53(45.225.75.8) (UDP)
;; WHEN: Mon Jul 15 09:48:10 AEST 2024
;; MSG SIZE rcvd: 88
[ant:~/git/bind9] marka%
Mark
alpha_one_x86/BRULE Herman<alpha_one_...@first-world.info>
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server
management
IT, OS, technologies, research & development, security and business department
On 7/12/24 19:01, Mark Andrews wrote:
On 13 Jul 2024, at 04:38, Herman Brule via bind-users<bind-users@lists.isc.org>
wrote:
Because the customer are into IPv6 zone
Well all zones should be served by both IPv4 servers and IPv6 servers. IPv6 is
nearly 30 years old now. There are
sites that are IPv6 only because they would prefer to not have to run
everything through 2 or 3 layers of NAT when
they don’t need it at all for IPv6 and would really like to not have to send
all there DNS queries though NAT64 boxes.
And the EDGE router connecting IPv4 and IPv6 is internal to the data center
company, not accessible for the customer.
Forward zone to edge will be more complex, it's more simple just forward the
query.
Thanks for you observation, but I know, I doing this quickly, I will keep like
this for now, this will produce only problem for availability if the server is
down.
Except you are wrong. You are writing here because it *is* causing you and
everyone else a problem. The correct way to
fix this is to transfer the zone contents to the listed primary servers if you
are using nameservers. Alternatively
don’t run nameservers at all but use IP level proxies. Either the whole address
or port forward 53/TCP and 53/UDP.
alpha_one_x86/BRULE Herman<alpha_one_...@first-world.info>
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server
management
IT, OS, technologies, research & development, security and business department
On 7/12/24 14:28, Marco Moock wrote:
Am 12.07.2024 um 14:13:03 Uhr schrieb Herman Brule via bind-users:
bind to my proxy from IPv4 to IPv6 zone
Why don't you simply run multiple authoritative servers, some only
accessible by IPv6, some dual-stack?
They are independent of each other and only the zone transfer need to
work.
I also see some strange things:
m@ryz:~$ host 811.vps.confiared.com.
811.vps.CONFIARED.com has address 45.225.75.8
811.vps.CONFIARED.com has IPv6 address 2803:1920::c:1963
m@ryz:~$ host 811b.vps.confiared.com.
811b.vps.CONFIARED.com is an alias for 811.vps.confiared.com.
811.vps.CONFIARED.com has address 45.225.75.8
811.vps.CONFIARED.com has IPv6 address 2803:1920::c:1963
m@ryz:~$
You should have redundant servers and not 2 NS records that point to
the same machine.
Please fix that first and update your glue records.
--
Visithttps://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us athttps://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
<ore.org.bo.db>
15-Jul-2024 08:45:58.989 starting BIND 9.18.24-1-Debian (Extended Support
Version) <id:>
15-Jul-2024 08:45:58.989 running on Linux x86_64 6.1.0-22-amd64 #1 SMP
PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21)
15-Jul-2024 08:45:58.989 built with '--build=x86_64-linux-gnu' '--prefix=/usr'
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man'
'--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var'
'--disable-option-checking' '--disable-silent-rules'
'--libdir=${prefix}/lib/x86_64-linux-gnu' '--runstatedir=/run'
'--disable-maintainer-mode' '--disable-dependency-tracking'
'--libdir=/usr/lib/x86_64-linux-gnu' '--sysconfdir=/etc/bind'
'--with-python=python3' '--localstatedir=/' '--enable-threads'
'--enable-largefile' '--with-libtool' '--enable-shared' '--disable-static'
'--with-gost=no' '--with-openssl=/usr' '--with-gssapi=yes' '--with-libidn2'
'--with-json-c' '--with-lmdb=/usr' '--with-gnu-ld' '--with-maxminddb'
'--with-atf=no' '--enable-ipv6' '--enable-rrl' '--enable-filter-aaaa'
'--disable-native-pkcs11' '--enable-dnstap' 'build_alias=x86_64-linux-gnu'
'CFLAGS=-g -O2 -ffile-prefix-map=/build/reproducible-path/bind9-9.18.24=.
-fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing
-fno-delete-null-pointer-checks -DNO_VERSION_DATE -DDIG_SIGCHASE'
'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'
15-Jul-2024 08:45:58.989 running as: named -g -d 10
15-Jul-2024 08:45:58.989 compiled by GCC 12.2.0
15-Jul-2024 08:45:58.989 compiled with OpenSSL version: OpenSSL 3.0.11 19 Sep
2023
15-Jul-2024 08:45:58.989 linked to OpenSSL version: OpenSSL 3.0.13 30 Jan 2024
15-Jul-2024 08:45:58.989 compiled with libuv version: 1.44.2
15-Jul-2024 08:45:58.989 linked to libuv version: 1.44.2
15-Jul-2024 08:45:58.989 compiled with libxml2 version: 2.9.14
15-Jul-2024 08:45:58.989 linked to libxml2 version: 20914
15-Jul-2024 08:45:58.989 compiled with json-c version: 0.16
15-Jul-2024 08:45:58.989 linked to json-c version: 0.16
15-Jul-2024 08:45:58.989 compiled with zlib version: 1.2.13
15-Jul-2024 08:45:58.989 linked to zlib version: 1.2.13
15-Jul-2024 08:45:58.989 ----------------------------------------------------
15-Jul-2024 08:45:58.989 BIND 9 is maintained by Internet Systems Consortium,
15-Jul-2024 08:45:58.989 Inc. (ISC), a non-profit 501(c)(3) public-benefit
15-Jul-2024 08:45:58.989 corporation. Support and training for BIND 9 are
15-Jul-2024 08:45:58.989 available at https://www.isc.org/support
15-Jul-2024 08:45:58.989 ----------------------------------------------------
15-Jul-2024 08:45:58.989 found 4 CPUs, using 4 worker threads
15-Jul-2024 08:45:58.989 using 4 UDP listeners per interface
15-Jul-2024 08:45:58.997 Registering DLZ_dlopen driver
15-Jul-2024 08:45:58.997 Registering SDLZ driver 'dlopen'
15-Jul-2024 08:45:58.997 Registering DLZ driver 'dlopen'
15-Jul-2024 08:45:58.997 DNSSEC algorithms: RSASHA1 NSEC3RSASHA1 RSASHA256
RSASHA512 ECDSAP256SHA256 ECDSAP384SHA384 ED25519 ED448
15-Jul-2024 08:45:58.997 DS algorithms: SHA-1 SHA-256 SHA-384
15-Jul-2024 08:45:58.997 HMAC algorithms: HMAC-MD5 HMAC-SHA1 HMAC-SHA224
HMAC-SHA256 HMAC-SHA384 HMAC-SHA512
15-Jul-2024 08:45:58.997 TKEY mode 2 support (Diffie-Hellman): yes
15-Jul-2024 08:45:58.997 TKEY mode 3 support (GSS-API): yes
15-Jul-2024 08:45:59.001 loading configuration from '/etc/bind/named.conf'
15-Jul-2024 08:45:59.001 reading built-in trust anchors from file
'/etc/bind/bind.keys'
15-Jul-2024 08:45:59.001 exclusive task mode: starting
15-Jul-2024 08:45:59.001 exclusive task mode: started
15-Jul-2024 08:45:59.001 set maximum stack size to 18446744073709551615: success
15-Jul-2024 08:45:59.001 set maximum data size to 18446744073709551615: success
15-Jul-2024 08:45:59.001 set maximum core size to 18446744073709551615: success
15-Jul-2024 08:45:59.001 set maximum open files to 18446744073709551615: success
15-Jul-2024 08:45:59.001 looking for GeoIP2 databases in '/usr/share/GeoIP'
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoIP2-Country.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoLite2-Country.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoIP2-City.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoLite2-City.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoIP2-ASN.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoLite2-ASN.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoIP2-ISP.mmdb' (status 1)
15-Jul-2024 08:45:59.001 unable to open GeoIP2 database
'/usr/share/GeoIP/GeoIP2-Domain.mmdb' (status 1)
15-Jul-2024 08:45:59.001 using default UDP/IPv4 port range: [32768, 60999]
15-Jul-2024 08:45:59.001 using default UDP/IPv6 port range: [32768, 60999]
15-Jul-2024 08:45:59.005 listening on IPv4 interface lo, 45.225.75.241#53
15-Jul-2024 08:45:59.005 creating IPv4 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv4 interface enp2s0, 199.38.247.210#53
15-Jul-2024 08:45:59.005 creating IPv4 interface enp2s0 failed; interface
ignored
15-Jul-2024 08:45:59.005 IPv6 socket API is incomplete; explicitly binding to
each IPv6 address separately
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:9#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:8#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:7#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:6#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:5#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:4#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:3#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:2#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:1#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo,
2803:1920::b4b2:5f61:d37f:0#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface lo, ::1#53
15-Jul-2024 08:45:59.005 creating IPv6 interface lo failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface enp2s0, 2606:d280::4a#53
15-Jul-2024 08:45:59.005 creating IPv6 interface enp2s0 failed; interface
ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface enp2s0,
fe80::be5f:f4ff:feaf:6e51%2#53
15-Jul-2024 08:45:59.005 creating IPv6 interface enp2s0 failed; interface
ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface orion,
2803:1920::9c8f:e163:d79:0#53
15-Jul-2024 08:45:59.005 creating IPv6 interface orion failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface orion,
fe80::8c49:9979:5ca1:26c6%4#53
15-Jul-2024 08:45:59.005 creating IPv6 interface orion failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface hades,
2803:1920::9c8f:e163:d6d:0#53
15-Jul-2024 08:45:59.005 creating IPv6 interface hades failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface hades,
fe80::94f3:47ff:fea3:5687%6#53
15-Jul-2024 08:45:59.005 creating IPv6 interface hades failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface dc3l1,
2803:1920::9c8f:e163:d77:b#53
15-Jul-2024 08:45:59.005 creating IPv6 interface dc3l1 failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface dc3l1,
fe80::33ba:486d:c987:9706%7#53
15-Jul-2024 08:45:59.005 creating IPv6 interface dc3l1 failed; interface ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface hadesbis,
2803:1920::9c8f:e163:d6e:0#53
15-Jul-2024 08:45:59.005 creating IPv6 interface hadesbis failed; interface
ignored
15-Jul-2024 08:45:59.005 listening on IPv6 interface hadesbis,
fe80::94f3:47ff:e0a6:53ce%9#53
15-Jul-2024 08:45:59.005 creating IPv6 interface hadesbis failed; interface
ignored
15-Jul-2024 08:45:59.005 generating session key for dynamic DNS
15-Jul-2024 08:45:59.005 none:228: dnssec-policy: load policy 'default'
15-Jul-2024 08:45:59.005 none:246: dnssec-policy: load policy 'insecure'
15-Jul-2024 08:45:59.005 sizing zone task pool based on 12 zones
15-Jul-2024 08:45:59.005 zone_settimer: zone localhost/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone localhost/IN: settimer inactive
15-Jul-2024 08:45:59.005 zone_settimer: zone 127.in-addr.arpa/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone 127.in-addr.arpa/IN: settimer
inactive
15-Jul-2024 08:45:59.005 zone_settimer: zone 0.in-addr.arpa/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone 0.in-addr.arpa/IN: settimer
inactive
15-Jul-2024 08:45:59.005 zone_settimer: zone 255.in-addr.arpa/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone 255.in-addr.arpa/IN: settimer
inactive
15-Jul-2024 08:45:59.005 zone_settimer: zone 75.225.45.in-addr.arpa/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone 75.225.45.in-addr.arpa/IN:
settimer inactive
15-Jul-2024 08:45:59.005 zone_settimer: zone 0.2.9.1.3.0.8.2.ip6.arpa/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone 0.2.9.1.3.0.8.2.ip6.arpa/IN:
settimer inactive
15-Jul-2024 08:45:59.005 zone_settimer: zone ore.org.bo/IN: enter
15-Jul-2024 08:45:59.005 zone_settimer: zone ore.org.bo/IN: settimer inactive
15-Jul-2024 08:45:59.005 none:100: 'max-cache-size 90%' - setting to 7077MB
(out of 7863MB)
15-Jul-2024 08:45:59.005 dns_requestmgr_create
15-Jul-2024 08:45:59.005 dns_requestmgr_create: 0x7fcbcbe4b1c0
15-Jul-2024 08:45:59.005 dns_requestmgr_whenshutdown
15-Jul-2024 08:45:59.005 obtaining root key for view _default from
'/etc/bind/bind.keys'
15-Jul-2024 08:45:59.005 set up managed keys zone for view _default, file
'managed-keys.bind'
15-Jul-2024 08:45:59.009 automatic empty zone: 10.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 16.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 17.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 18.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 19.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 20.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 21.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 22.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 23.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 24.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 25.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 26.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 27.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 28.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 29.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 30.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 31.172.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 168.192.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 64.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 65.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 66.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 67.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 68.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 69.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 70.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 71.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 72.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 73.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 74.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 75.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 76.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 77.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 78.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 79.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 80.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 81.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 82.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 83.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 84.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 85.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 86.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 87.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 88.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 89.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 90.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 91.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 92.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 93.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 94.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 95.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 96.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 97.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 98.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 99.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 100.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 101.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 102.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 103.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 104.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 105.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 106.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 107.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 108.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 109.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 110.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 111.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 112.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 113.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 114.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 115.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 116.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 117.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 118.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 119.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 120.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 121.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 122.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 123.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 124.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 125.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 126.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 127.100.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 254.169.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 2.0.192.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 100.51.198.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 113.0.203.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone:
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: D.F.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 8.E.F.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 9.E.F.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: A.E.F.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: B.E.F.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: EMPTY.AS112.ARPA
15-Jul-2024 08:45:59.009 automatic empty zone: HOME.ARPA
15-Jul-2024 08:45:59.009 zone_settimer: zone version.bind/CH: enter
15-Jul-2024 08:45:59.009 zone_settimer: zone version.bind/CH: settimer inactive
15-Jul-2024 08:45:59.009 zone_settimer: zone hostname.bind/CH: enter
15-Jul-2024 08:45:59.009 zone_settimer: zone hostname.bind/CH: settimer inactive
15-Jul-2024 08:45:59.009 zone_settimer: zone authors.bind/CH: enter
15-Jul-2024 08:45:59.009 zone_settimer: zone authors.bind/CH: settimer inactive
15-Jul-2024 08:45:59.009 zone_settimer: zone id.server/CH: enter
15-Jul-2024 08:45:59.009 zone_settimer: zone id.server/CH: settimer inactive
15-Jul-2024 08:45:59.009 dns_requestmgr_create
15-Jul-2024 08:45:59.009 dns_requestmgr_create: 0x7fcbcbe4b380
15-Jul-2024 08:45:59.009 dns_requestmgr_whenshutdown
15-Jul-2024 08:45:59.009 configuring command channel from '/etc/bind/rndc.key'
15-Jul-2024 08:45:59.009 couldn't add command channel 127.0.0.1#953: permission
denied
15-Jul-2024 08:45:59.009 configuring command channel from '/etc/bind/rndc.key'
15-Jul-2024 08:45:59.009 couldn't add command channel ::1#953: permission denied
15-Jul-2024 08:45:59.009 not using config file logging statement for logging
due to -g option
15-Jul-2024 08:45:59.009 checking logging configuration failed: permission
denied
15-Jul-2024 08:45:59.009 exclusive task mode: ending
15-Jul-2024 08:45:59.009 exclusive task mode: ended
15-Jul-2024 08:45:59.009 load_configuration: permission denied
15-Jul-2024 08:45:59.009 exclusive task mode: starting
15-Jul-2024 08:45:59.009 exclusive task mode: started
15-Jul-2024 08:45:59.009 loading configuration: permission denied
15-Jul-2024 08:45:59.009 exiting (due to fatal error)
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
