BIND issueshttps://gitlab.isc.org/isc-projects/bind9/-/issues2023-11-02T16:26:07Zhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2734dns64 processing of stale AAAA doesn't use a non-stale A2023-11-02T16:26:07ZEvan Huntdns64 processing of stale AAAA doesn't use a non-stale AIn [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5102#note_216731) in !5102, @michal pointed out an edge case in stale-data/dns64 processing that may be a bug:
- we're searching for AAAA, but the auth server is...In [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5102#note_216731) in !5102, @michal pointed out an edge case in stale-data/dns64 processing that may be a bug:
- we're searching for AAAA, but the auth server is slow
- we reach the stale answer timeout, but we don't have a stale AAAA in the cache
- but we have a _current_ A record in the cache
- ...but dns64 can't use it to synthesize a reply, because when we're processing a stale timeout we only look for _stale_ data.
This can be observed by applying these changes to the test code that was introduced in that MR:
```
diff --git a/bin/tests/system/serve-stale/ans2/ans.pl b/bin/tests/system/serve-stale/ans2/ans.pl
index a046417e09c..5e11f22cf6a 100644
--- a/bin/tests/system/serve-stale/ans2/ans.pl
+++ b/bin/tests/system/serve-stale/ans2/ans.pl
@@ -119,7 +119,7 @@ sub reply_handler {
$rcode = "NOERROR";
} elsif ($qname eq "a-only.example") {
if ($qtype eq "A") {
- my $rr = new Net::DNS::RR("a-only.example 2 IN A $localaddr");
+ my $rr = new Net::DNS::RR("a-only.example 5 IN A $localaddr");
push @ans, $rr;
} else {
my $rr = new Net::DNS::RR($negSOA);
diff --git a/bin/tests/system/serve-stale/tests.sh b/bin/tests/system/serve-stale/tests.sh
index b287f8c1f07..7ac0288d329 100755
--- a/bin/tests/system/serve-stale/tests.sh
+++ b/bin/tests/system/serve-stale/tests.sh
@@ -2216,7 +2216,7 @@ $DIG -p ${PORT} @10.53.0.2 txt disable > /dev/null
# wait two seconds for the previous answer to become stale
sleep 2
# resend the query and wait in the background; we should get a stale answer
-$DIG -p ${PORT} @10.53.0.3 a-only.example AAAA > dig.out.2.test$n &
+$DIG -p ${PORT} +tries=1 @10.53.0.3 a-only.example AAAA > dig.out.2.test$n &
# re-enable queries after a pause, so the server gets a real answer too
sleep 2
$DIG -p ${PORT} @10.53.0.2 txt enable > /dev/null
```Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2744warning: checkhints: unable to get root NS rrset from cache: not found2024-03-27T00:34:35ZCathy Almondwarning: checkhints: unable to get root NS rrset from cache: not foundPeriodically we see reports of resolvers that are failing to respond to clients successfully, perhaps with a build-up of recursive clients, inbound UDP packet drops, late and missing query responses and so on. Rebooting the server entir...Periodically we see reports of resolvers that are failing to respond to clients successfully, perhaps with a build-up of recursive clients, inbound UDP packet drops, late and missing query responses and so on. Rebooting the server entirely usually fixes the problem - for a time. Flushing cache may also buy some relief, but generally this does not last as long as if the server is rebooted entirely.
Plus one symptom in the logs - repeated spates of messages like this:
```
31-May-2021 16:08:38.110 general: warning: checkhints: unable to get root NS rrset from cache: not found
31-May-2021 16:08:41.110 general: warning: checkhints: unable to get root NS rrset from cache: not found
31-May-2021 16:08:42.151 general: warning: checkhints: unable to get root NS rrset from cache: not found
```
This error message occurs when the root nameservers have just been primed, but when checkhints goes to look at them, they're no longer available in cache (have been expired, possible also removed), all in a very short period of time.
Reports of this have been seen intermittently for many years and from many versions of BIND 9. Typically (in the older reports) this was a rare occurrence seen on a resolver that had been running for a long time; months, possibly years. Therefore after rebooting, the error and the problem was never seen again (or at least not within the shelf-life of the admin who reported it to us originally).
We suspect that what is happening is that the cache structure and content have become unmaintainable over a long period of content being added, expired and removed, and that there it's become impossible to add new RRsets to cache without using expiring existing content because of max-cache-size. The cache tree structure itself also occupies memory, and we've seen a few instances where a long-lived cache has become 'straggly' but also sparsely populated.
What we haven't been able to catch (yet), is the exact path taken that causes this error to be logged, although we have been hoping that improved stats, along with a `catch it earlier` assertion (the server anyway needs to be restarted when it has reached this state) might help. See #2082 .
We have also seen that in one or two instances of this warning being logged, in addition there was a problem reaching some of the root nameserver addresses listed in the root hints and used for priming. Either the root hints were out of date and an older IP address was unreachable, or there were local routing issues (typically IPv6-related) reaching some root server addresses. **This shouldn't be a problem**, per the way that root hints priming is designed, _but 'fixing' the root hints appears to have made the problem go away in some instances, as has fixing the routing and unreachability of some root hint addresses._
----
For anyone experiencing this problem for the first time, the likelihood is that one or more things have changed in your operating environment, and that these are causing cache content to be more substantial than before, or potentially distributed differently. For example:
- Installing a version of BIND that has `stale-cache-enable yes` by default
- An increase in client queries overall
- Client query patterns changing - perhaps causing a higher rate than usual of cached negative responses
- An increase in dual-stack clients querying for AAAA records
- An increase in client querying for HTTPS records
- A new client application that uses DNS-based probing
- Clients using a tunnelling-over-DNS service
- Using a client filtering service that operates by means of resolving the original client query first by appending another private zone name to it and checking the response status before allowing the original query to pass - thus adding the filtering RRsets to cache as well as the actual client query responses.
Currently, clues may be found in the BIND statistics and also in a dump of cache.
Firstly, these counters (available either from the output from `rndc stats` or using the xml or json statistics interface), can be a good indicator that there is too much cache cleaning taking place due to memory pressure, versus RRset TTL expiration:
DeleteLRU - "cache records deleted due to memory exhaustion"
DeleteTTL - "cache records deleted due to TTL expiration"
These are counters, therefore although seeing DeleteLRU far exceeding DeleteTTL in a single snapshot of the stats is a good indicator that all is not well with cache, ideally you want to monitor the trend over time.
Also these :
HeapMemInUse - "cache heap memory in use"
TreeMemInUse - "cache tree memory in use"
HeapMemMax - "cache heap highest memory in use"
TreeMemMax - "cache tree highest memory in use"
All of the above are gauges - they tell you 'this is where we are now', so a snapshot can be useful, as well as monitoring pattern over time. The 'Max' is a high water mark.
Aside: don't be tempted to look at either of these - they are not useful operationally and aren't counting what you might think they are from their names:
HeapMemTotal - "cache heap memory total"
TreeMemTotal - "cache tree memory total"
And finally, there are counters available of what's in cache currrently by RType. These are prefixed with `!` for counters of NXRRSET (pseudo RR indicating that a name that was queried existed but the type didn't), `#` for stale content, and `~` for content that has expired and is waiting on housekeeping/deletion.
If there is any kind of unexpected skew, it might be worth dumping cache to see what's in there.
And then decide - is it just that max-cache-size is now insufficient, or is that something else needs to be done to reduce cache content.May 2024 (9.18.27, 9.18.27-S1, 9.19.24)Mark AndrewsMark Andrewshttps://gitlab.isc.org/isc-projects/bind9/-/issues/2748Could more detail be added to the query log to show the query protocol used (...2022-03-22T09:49:26ZRichard NealCould more detail be added to the query log to show the query protocol used (eg Do53, DoT, DoH)?### Description
It would be useful if BIND could log the query protocol used by the client - e.g. Do53, DoT, DoH. This would allow system administrators to understand the proportion of different types of queries and to help determine an...### Description
It would be useful if BIND could log the query protocol used by the client - e.g. Do53, DoT, DoH. This would allow system administrators to understand the proportion of different types of queries and to help determine any additional resource overhead (e.g. the computational resource overhead of encryption for DoT or DoH)
### Request
The logging statement grammar should be enhanced to allow the system administrator to (optionally?) include the protocol type for the query. If the system administrator chooses to enable protocol logging then it may be preferable to use a simple integer value for the chosen field, eg:
1 = Do53, 2 = DoT, 3 = DoH (non-TLS, eg behind HTTPS load balancer), 4 = DoH (TLS)
This would allow for future protocols at a later date
### Links / references
I have looked in the BIND 9.17 ARM and can see no reference to BIND being able to log the query protocol used by the client, but I am happy to be corrected if this feature already exists.
Thanks,
Richard.BIND 9.19.xhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2761Excessive interval between zone transfer retries after failure2021-06-09T18:02:44ZEverett FultonExcessive interval between zone transfer retries after failureFrom https://support.isc.org/Ticket/Display.html?id=18577
A customer using 9.11.30-S1 reports intermittent zone transfers with "failed setting up socket: address in use" being logged. This would not be a serious issue, except that more...From https://support.isc.org/Ticket/Display.html?id=18577
A customer using 9.11.30-S1 reports intermittent zone transfers with "failed setting up socket: address in use" being logged. This would not be a serious issue, except that more than 10 minutes can pass before a retry.https://gitlab.isc.org/isc-projects/bind9/-/issues/2766Implement TCP fallback on no cookie2023-11-02T16:21:21ZMark AndrewsImplement TCP fallback on no cookieFallback to TCP on no COOKIE has been flagged as a future extension for a while.
Implement this.
Default to `true` with the ability to disable via named.conf.Fallback to TCP on no COOKIE has been flagged as a future extension for a while.
Implement this.
Default to `true` with the ability to disable via named.conf.Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2771named is unable to initialize krb context on NetBSD 9.22022-03-01T09:39:48ZMichal Nowaknamed is unable to initialize krb context on NetBSD 9.2`named` is unable to initialize krb context on NetBSD 9.2, it start's with 9.17.13, 9.16.16, and 9.11.32 as seen in the `nsupdate` system test:
```
failed gss_import_name: GSSAPI error: Major = Miscellaneous failure (see text), Minor = ...`named` is unable to initialize krb context on NetBSD 9.2, it start's with 9.17.13, 9.16.16, and 9.11.32 as seen in the `nsupdate` system test:
```
failed gss_import_name: GSSAPI error: Major = Miscellaneous failure (see text), Minor = unknown mech-code 6 for mech unknown.
```
```
checking for krb5-config... /usr/bin/krb5-config
checking for gssapi libraries... -lgssapi
checking for gssapi/gssapi.h... yes
checking for gssapi/gssapi_krb5.h... yes
checking for gssapi_krb5.h... no
checking for gss_acquire_cred... yes
checking for krb5 libraries... -lkrb5
checking for krb5/krb5.h... yes
checking for krb5_init_context... yes
```
<details>
```
14-Jun-2021 15:34:46.962 starting BIND 9.17.13 (Development Release) <id:8d36cac>
14-Jun-2021 15:34:46.962 running on NetBSD amd64 9.2 NetBSD 9.2 (GENERIC) #0: Wed May 12 13:15:55 UTC 2021 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC
14-Jun-2021 15:34:46.962 built with '--enable-developer' '--enable-dnstap' '--with-libidn2' '--disable-maintainer-mode' '--enable-option-checking=fatal' '--with-cmocka' '--with-libxml2' '--with-json-c' 'CC=clang' 'CFLAGS=-fno-omit-frame-pointer -fno-optimize-sibling-calls -O1 -g -Wall -Wextra'
14-Jun-2021 15:34:46.963 running as: named -D nsupdate-ns10 -X named.lock -m record,size,mctx -c named.conf -d 99 -g -U 4 -T maxcachesize\=2097152
14-Jun-2021 15:34:46.963 compiled by CLANG Clang 10.0.1
14-Jun-2021 15:34:46.963 compiled with OpenSSL version: OpenSSL 1.1.1k 25 Mar 2021
14-Jun-2021 15:34:46.963 linked to OpenSSL version: OpenSSL 1.1.1k 25 Mar 2021
14-Jun-2021 15:34:46.963 compiled with libxml2 version: 2.9.12
14-Jun-2021 15:34:46.963 linked to libxml2 version: 20912
14-Jun-2021 15:34:46.963 compiled with json-c version: 0.15
14-Jun-2021 15:34:46.963 linked to json-c version: 0.15
14-Jun-2021 15:34:46.963 compiled with zlib version: 1.2.10
14-Jun-2021 15:34:46.963 linked to zlib version: 1.2.10
14-Jun-2021 15:34:46.963 ----------------------------------------------------
14-Jun-2021 15:34:46.963 BIND 9 is maintained by Internet Systems Consortium,
14-Jun-2021 15:34:46.963 Inc. (ISC), a non-profit 501(c)(3) public-benefit
14-Jun-2021 15:34:46.963 corporation. Support and training for BIND 9 are
14-Jun-2021 15:34:46.963 available at https://www.isc.org/support
14-Jun-2021 15:34:46.963 ----------------------------------------------------
14-Jun-2021 15:34:46.963 found 4 CPUs, using 4 worker threads
14-Jun-2021 15:34:46.963 using 4 UDP listeners per interface
14-Jun-2021 15:34:46.976 using up to 21000 sockets
14-Jun-2021 15:34:46.976 Registering DLZ_dlopen driver
14-Jun-2021 15:34:46.976 Registering SDLZ driver 'dlopen'
14-Jun-2021 15:34:46.976 Registering DLZ driver 'dlopen'
14-Jun-2021 15:34:46.978 socket 0x78e8a0047010: created
14-Jun-2021 15:34:46.978 socket 0x78e8a0047010: socket_recv: event 0x78e8a0047190 -> task 0x78e8a0112010
14-Jun-2021 15:34:46.978 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -3 for socket 40
14-Jun-2021 15:34:46.978 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.978 config.c: option 'trust-anchor-telemetry' is experimental and subject to change in the future
14-Jun-2021 15:34:46.979 loading configuration from '/home/newman/bind9/bin/tests/system/nsupdate/ns10/named.conf'
14-Jun-2021 15:34:46.979 reading built-in trust anchors from file '/usr/local/etc/bind.keys'
14-Jun-2021 15:34:46.979 set maximum stack size to 134217728: success
14-Jun-2021 15:34:46.979 set maximum data size to 8589934592: success
14-Jun-2021 15:34:46.979 set maximum core size to 9223372036854775807: success
14-Jun-2021 15:34:46.979 set maximum open files to 18446744073709551615: success
14-Jun-2021 15:34:46.980 max open files (3404) is smaller than max sockets (21000)
14-Jun-2021 15:34:46.980 using default UDP/IPv4 port range: [49152, 65535]
14-Jun-2021 15:34:46.980 using default UDP/IPv6 port range: [49152, 65535]
14-Jun-2021 15:34:46.981 IPv6 socket API is incomplete; explicitly binding to each IPv6 address separately
14-Jun-2021 15:34:46.981 listening on IPv6 interface vioif0, fe80::5054:ff:fe11:1546%1#24102
14-Jun-2021 15:34:46.981 listening on IPv6 interface lo0, ::1#24102
14-Jun-2021 15:34:46.981 listening on IPv6 interface lo0, fe80::1%2#24102
14-Jun-2021 15:34:46.982 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::1#24102
14-Jun-2021 15:34:46.982 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::2#24102
14-Jun-2021 15:34:46.982 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::3#24102
14-Jun-2021 15:34:46.983 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::4#24102
14-Jun-2021 15:34:46.983 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::5#24102
14-Jun-2021 15:34:46.983 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::6#24102
14-Jun-2021 15:34:46.984 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::7#24102
14-Jun-2021 15:34:46.984 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::8#24102
14-Jun-2021 15:34:46.984 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::9#24102
14-Jun-2021 15:34:46.984 listening on IPv4 interface lo0, 10.53.0.10#24102
14-Jun-2021 15:34:46.985 listening on IPv6 interface lo0, fd92:7065:b8e:ffff::10#24102
14-Jun-2021 15:34:46.985 listening on IPv6 interface lo0, fd92:7065:b8e:99ff::1#24102
14-Jun-2021 15:34:46.985 listening on IPv6 interface lo0, fd92:7065:b8e:99ff::2#24102
14-Jun-2021 15:34:46.986 listening on IPv6 interface lo0, fd92:7065:b8e:ff::1#24102
14-Jun-2021 15:34:46.986 listening on IPv6 interface lo0, fd92:7065:b8e:ff::2#24102
14-Jun-2021 15:34:46.987 generating session key for dynamic DNS
14-Jun-2021 15:34:46.988 sizing zone task pool based on 2 zones
14-Jun-2021 15:34:46.988 zone_settimer: zone in-addr.arpa/IN: enter
14-Jun-2021 15:34:46.988 zone_settimer: zone in-addr.arpa/IN: settimer inactive
14-Jun-2021 15:34:46.988 zone_settimer: zone example.com/IN: enter
14-Jun-2021 15:34:46.988 zone_settimer: zone example.com/IN: settimer inactive
14-Jun-2021 15:34:46.989 sendmsg: Protocol option not available
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4d90: created
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4d90 10.53.0.10#0: bound
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4d90: destroying
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.989 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cb800
14-Jun-2021 15:34:46.989 dispatch 0x78e89f4cb800: created task 0x78e89fdb5b30
14-Jun-2021 15:34:46.989 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cb200
14-Jun-2021 15:34:46.989 dispatch 0x78e89f4cb200: created task 0x78e89fdb9330
14-Jun-2021 15:34:46.989 res 0x78e8a005c010: create
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.989 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cac00
14-Jun-2021 15:34:46.989 dispatch 0x78e89f4cac00: created task 0x78e89f476c10
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.989 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4ca600
14-Jun-2021 15:34:46.989 dispatch 0x78e89f4ca600: created task 0x78e89f47a410
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.989 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4ca000
14-Jun-2021 15:34:46.989 dispatch 0x78e89f4ca000: created task 0x78e89f45ec10
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.989 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.989 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cfa00
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4cfa00: created task 0x78e89f462410
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cf400
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4cf400: created task 0x78e89f44bc10
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cee00
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4cee00: created task 0x78e89f44f410
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4ce800
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4ce800: created task 0x78e89f42fc10
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4ce200
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4ce200: created task 0x78e89f433410
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cdc00
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4cdc00: created task 0x78e89f1fac10
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.990 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.990 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cd600
14-Jun-2021 15:34:46.990 dispatch 0x78e89f4cd600: created task 0x78e89f1fe410
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.990 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cd000
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4cd000: created task 0x78e89f1e7c10
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d2a00
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d2a00: created task 0x78e89f1eb410
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d2400
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d2400: created task 0x78e89f1cbc10
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d1e00
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d1e00: created task 0x78e89f1cf410
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: created
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10 10.53.0.10#0: bound
14-Jun-2021 15:34:46.991 socket 0x78e89f4c4f10: destroying
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.991 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d1800
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d1800: created task 0x78e89f1bec10
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d1200
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d1200: created task 0x78e89f1c2410
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d0c00
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d0c00: created task 0x78e89f1a8c10
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d0600
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d0600: created task 0x78e89f1ac410
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4d0000
14-Jun-2021 15:34:46.991 dispatch 0x78e89f4d0000: created task 0x78e89f195c10
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e6a00
14-Jun-2021 15:34:46.991 dispatch 0x78e89f5e6a00: created task 0x78e89f199410
14-Jun-2021 15:34:46.991 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e6400
14-Jun-2021 15:34:46.991 dispatch 0x78e89f5e6400: created task 0x78e89f179c10
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e5e00
14-Jun-2021 15:34:46.992 dispatch 0x78e89f5e5e00: created task 0x78e89f17d410
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e5800
14-Jun-2021 15:34:46.992 dispatch 0x78e89f5e5800: created task 0x78e89f169c10
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e5200
14-Jun-2021 15:34:46.992 dispatch 0x78e89f5e5200: created task 0x78e89f16d410
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e4c00
14-Jun-2021 15:34:46.992 dispatch 0x78e89f5e4c00: created task 0x78e89f155c10
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e4600
14-Jun-2021 15:34:46.992 dispatch 0x78e89f5e4600: created task 0x78e89f159410
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f5e4000
14-Jun-2021 15:34:46.992 dispatch 0x78e89f5e4000: created task 0x78e89f139c10
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89fcb2a00
14-Jun-2021 15:34:46.992 dispatch 0x78e89fcb2a00: created task 0x78e89f13d410
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89fcb2400
14-Jun-2021 15:34:46.992 dispatch 0x78e89fcb2400: created task 0x78e89f126c10
14-Jun-2021 15:34:46.992 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89fcb1e00
14-Jun-2021 15:34:46.992 dispatch 0x78e89fcb1e00: created task 0x78e89f12a410
14-Jun-2021 15:34:46.992 dns_requestmgr_create
14-Jun-2021 15:34:46.992 dns_requestmgr_create: 0x78e89f0e1010
14-Jun-2021 15:34:46.992 dns_requestmgr_whenshutdown
14-Jun-2021 15:34:46.992 obtaining root key for view _default from '/usr/local/etc/bind.keys'
14-Jun-2021 15:34:46.993 set up managed keys zone for view _default, file 'managed-keys.bind'
14-Jun-2021 15:34:46.993 dispatch 0x78e89f4cb800: detach: refcount 2
14-Jun-2021 15:34:46.993 dispatch 0x78e89f4cb200: detach: refcount 2
14-Jun-2021 15:34:46.993 zone_settimer: zone version.bind/CH: enter
14-Jun-2021 15:34:46.993 zone_settimer: zone version.bind/CH: settimer inactive
14-Jun-2021 15:34:46.993 zone_settimer: zone hostname.bind/CH: enter
14-Jun-2021 15:34:46.993 zone_settimer: zone hostname.bind/CH: settimer inactive
14-Jun-2021 15:34:46.993 zone_settimer: zone authors.bind/CH: enter
14-Jun-2021 15:34:46.993 zone_settimer: zone authors.bind/CH: settimer inactive
14-Jun-2021 15:34:46.993 zone_settimer: zone id.server/CH: enter
14-Jun-2021 15:34:46.993 zone_settimer: zone id.server/CH: settimer inactive
14-Jun-2021 15:34:46.993 socket 0x78e89f09f210: created
14-Jun-2021 15:34:46.993 socket 0x78e89f09f210 10.53.0.10#0: bound
14-Jun-2021 15:34:46.993 socket 0x78e89f09f210: destroying
14-Jun-2021 15:34:46.993 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a5800
14-Jun-2021 15:34:46.993 dispatch 0x78e89f0a5800: created task 0x78e89f11a150
14-Jun-2021 15:34:46.993 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.993 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.993 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a5200
14-Jun-2021 15:34:46.993 dispatch 0x78e89f0a5200: created task 0x78e89f11d950
14-Jun-2021 15:34:46.993 res 0x78e8a005c1d0: create
14-Jun-2021 15:34:46.993 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.993 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.993 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.994 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a4c00
14-Jun-2021 15:34:46.994 dispatch 0x78e89f0a4c00: created task 0x78e89f076230
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.994 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a4600
14-Jun-2021 15:34:46.994 dispatch 0x78e89f0a4600: created task 0x78e89f079a30
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.994 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a4000
14-Jun-2021 15:34:46.994 dispatch 0x78e89f0a4000: created task 0x78e89f05b230
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.994 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a9a00
14-Jun-2021 15:34:46.994 dispatch 0x78e89f0a9a00: created task 0x78e89f05ea30
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.994 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a9400
14-Jun-2021 15:34:46.994 dispatch 0x78e89f0a9400: created task 0x78e89f048230
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.994 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.994 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a8e00
14-Jun-2021 15:34:46.994 dispatch 0x78e89f0a8e00: created task 0x78e89f04ba30
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.994 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.995 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a8800
14-Jun-2021 15:34:46.995 dispatch 0x78e89f0a8800: created task 0x78e89edfb230
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.995 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a8200
14-Jun-2021 15:34:46.995 dispatch 0x78e89f0a8200: created task 0x78e89edfea30
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.995 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a7c00
14-Jun-2021 15:34:46.995 dispatch 0x78e89f0a7c00: created task 0x78e89edee230
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.995 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a7600
14-Jun-2021 15:34:46.995 dispatch 0x78e89f0a7600: created task 0x78e89edf1a30
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.995 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0a7000
14-Jun-2021 15:34:46.995 dispatch 0x78e89f0a7000: created task 0x78e89eddb230
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.995 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.995 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0aca00
14-Jun-2021 15:34:46.995 dispatch 0x78e89f0aca00: created task 0x78e89eddea30
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.995 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0ac400
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0ac400: created task 0x78e89edc8230
14-Jun-2021 15:34:46.996 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.996 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.996 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.996 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.996 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.996 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -5 for socket 513
14-Jun-2021 15:34:46.996 sockmgr 0x78e8a34db9d0 thread 1: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0abe00
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0abe00: created task 0x78e89edcba30
14-Jun-2021 15:34:46.996 socket 0x78e89f09f390: created
14-Jun-2021 15:34:46.996 socket 0x78e89f09f390 10.53.0.10#0: bound
14-Jun-2021 15:34:46.996 socket 0x78e89f09f390: destroying
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0ab800
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0ab800: created task 0x78e89edac230
14-Jun-2021 15:34:46.996 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -5 for socket 512
14-Jun-2021 15:34:46.996 sockmgr 0x78e8a34db9d0 thread 0: watcher got message -2 for socket -1
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0ab200
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0ab200: created task 0x78e89edafa30
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0aac00
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0aac00: created task 0x78e89ed9f230
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0aa600
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0aa600: created task 0x78e89eda2a30
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f0aa000
14-Jun-2021 15:34:46.996 dispatch 0x78e89f0aa000: created task 0x78e89ed89230
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c9a00
14-Jun-2021 15:34:46.996 dispatch 0x78e89f4c9a00: created task 0x78e89ed8ca30
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c9400
14-Jun-2021 15:34:46.996 dispatch 0x78e89f4c9400: created task 0x78e89ed7c230
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c8e00
14-Jun-2021 15:34:46.996 dispatch 0x78e89f4c8e00: created task 0x78e89ed7fa30
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c8800
14-Jun-2021 15:34:46.996 dispatch 0x78e89f4c8800: created task 0x78e89ed5a230
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c8200
14-Jun-2021 15:34:46.996 dispatch 0x78e89f4c8200: created task 0x78e89ed5da30
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c7c00
14-Jun-2021 15:34:46.996 dispatch 0x78e89f4c7c00: created task 0x78e89ed4a230
14-Jun-2021 15:34:46.996 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c7600
14-Jun-2021 15:34:46.997 dispatch 0x78e89f4c7600: created task 0x78e89ed4da30
14-Jun-2021 15:34:46.997 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4c7000
14-Jun-2021 15:34:46.997 dispatch 0x78e89f4c7000: created task 0x78e89ed37230
14-Jun-2021 15:34:46.997 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cca00
14-Jun-2021 15:34:46.997 dispatch 0x78e89f4cca00: created task 0x78e89ed3aa30
14-Jun-2021 15:34:46.997 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cc400
14-Jun-2021 15:34:46.997 dispatch 0x78e89f4cc400: created task 0x78e89ed1b230
14-Jun-2021 15:34:46.997 dispatchmgr 0x78e8a0ec7010: created UDP dispatcher 0x78e89f4cbe00
14-Jun-2021 15:34:46.997 dispatch 0x78e89f4cbe00: created task 0x78e89ed1ea30
14-Jun-2021 15:34:46.997 dns_requestmgr_create
14-Jun-2021 15:34:46.997 dns_requestmgr_create: 0x78e89f0e1790
14-Jun-2021 15:34:46.997 dns_requestmgr_whenshutdown
14-Jun-2021 15:34:46.997 dispatch 0x78e89f0a5800: detach: refcount 2
14-Jun-2021 15:34:46.997 dispatch 0x78e89f0a5200: detach: refcount 2
14-Jun-2021 15:34:46.997 Unable to initialise krb5 context
14-Jun-2021 15:34:46.997 failed gss_import_name: GSSAPI error: Major = Miscellaneous failure (see text), Minor = unknown mech-code 6 for mech unknown.
14-Jun-2021 15:34:46.998 configuring TKEY: failure
14-Jun-2021 15:34:46.998 load_configuration: failure
14-Jun-2021 15:34:46.998 loading configuration: failure
14-Jun-2021 15:34:46.998 exiting (due to fatal error)
```
</details>Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2772Update: Validation Easy Start Explained2023-11-02T16:26:07ZMark AndrewsUpdate: Validation Easy Start ExplainedThis section still references managed-keys as of 9.16.16. It needs to be updated to refer to `trust-anchors`.
Also `delv does not consult the managed-keys database maintained by named, which means that if either of the keys in /etc/bin...This section still references managed-keys as of 9.16.16. It needs to be updated to refer to `trust-anchors`.
Also `delv does not consult the managed-keys database maintained by named, which means that if either of the keys in /etc/bind.keys is revoked and rolled over, /etc/bind.keys must be updated to use DNSSEC validation in delv.` is out of date.Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2798named-checkconf -p does not print effective values2023-11-02T16:26:07ZPetr Špačekpspacek@isc.orgnamed-checkconf -p does not print effective values### Description
Bordeline bug and feature request:
`named-checkconf -p` does not print effective values but only how the _text_ was parsed.
Example:
`resolver-query-timeout 3;` is silently set to `10` by named, but named-checkconf stil...### Description
Bordeline bug and feature request:
`named-checkconf -p` does not print effective values but only how the _text_ was parsed.
Example:
`resolver-query-timeout 3;` is silently set to `10` by named, but named-checkconf still prints value `3`.
### Request
An option to print effective values would be useful, especially if it highlighted where effective value differs from the configured value.
Obviously this is hard to do. From what I see in code, config handling in server.c nad in named-checkconf is completely different. Inheritance rules limits are implemented as ad-hoc code in server.c.
### Links / references
*See also:*
* #1326;Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2803Add missing zone locks in dns_zone_get_.* functions2021-06-28T12:32:08ZMatthijs Mekkingmatthijs@isc.orgAdd missing zone locks in dns_zone_get_.* functionsSee https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5234#note_223073See https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5234#note_223073https://gitlab.isc.org/isc-projects/bind9/-/issues/2805Session persistence for forwarders2023-11-02T17:02:19ZPeter DaviesSession persistence for forwardersSession persistence for forwarders:
Where Bind is configured to use forwarding extensively or exclusively and the environment in which it is located precludes the use of udp as a transport protocol.
It may enhance throughput and limi...Session persistence for forwarders:
Where Bind is configured to use forwarding extensively or exclusively and the environment in which it is located precludes the use of udp as a transport protocol.
It may enhance throughput and limit resources utilisation if tcp sessions could be made persistent to some configurable degree.
Bind would need to be able to discover if there was an existing tcp session that could be (re)used when it needs to forward queries to some well known source.
[RT #18727](https://support.isc.org/Ticket/Display.html?id=18727)Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2806Remove AX_CHECK_OPENSSL2022-03-01T09:56:02ZOndřej SurýRemove AX_CHECK_OPENSSLIn favor of openssl.pcIn favor of openssl.pcNot plannedOndřej SurýOndřej Surýhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2828Compile fail on musl/arm32 since 9.16.82022-03-01T09:45:06ZEd WildgooseCompile fail on musl/arm32 since 9.16.8Hi, I'm building a gentoo based system on arm v7 32bit, using musl as my libc. I am hitting a compile error, that I have determined happens on 9.16.9 onwards, yet I can build fine with 9.16.8 and earlier
The specific error snippet I se...Hi, I'm building a gentoo based system on arm v7 32bit, using musl as my libc. I am hitting a compile error, that I have determined happens on 9.16.9 onwards, yet I can build fine with 9.16.8 and earlier
The specific error snippet I see is:
armv7a-unknown-linux-musleabihf-gcc -O2 -pipe -march=armv7-a -mfpu=neon-vfpv4 -mfloat-abi=hard -mno-unaligned-access -DDIG_SIGCHASE -pthread -fPIC -Wl,-O1 -Wl,--as-needed -L/usr/lib -Wl,--export-dynamic -o sample-async \
sample-async.o ../dns/libdns.a ../isccfg/libisccfg.a ../isc/libisc.a -lcrypto -luv -ldl
/usr/lib/gcc/armv7a-unknown-linux-musleabihf/10.3.0/../../../../armv7a-unknown-linux-musleabihf/bin/ld: ../isc/libisc.a(backtrace.o): in function `btcallback':
backtrace.c:(.text+0x50): undefined reference to `_Unwind_GetIP'
armv7a-unknown-linux-musleabihf-gcc -O2 -pipe -march=armv7-a -mfpu=neon-vfpv4 -mfloat-abi=hard -mno-unaligned-access -DDIG_SIGCHASE -pthread -fPIC -Wl,-O1 -Wl,--as-needed -L/usr/lib -Wl,--export-dynamic -o resolve \
resolve.o ../irs/libirs.a ../dns/libdns.a ../isccfg/libisccfg.a ../isc/libisc.a -lcrypto -luv -ldl
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:494: sample-gai] Error 1
make[1]: *** Waiting for unfinished jobs....
/usr/lib/gcc/armv7a-unknown-linux-musleabihf/10.3.0/../../../../armv7a-unknown-linux-musleabihf/bin/ld: ../isc/libisc.a(backtrace.o): in function `btcallback':
backtrace.c:(.text+0x50): undefined reference to `_Unwind_GetIP'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:502: sample-request] Error 1
/usr/lib/gcc/armv7a-unknown-linux-musleabihf/10.3.0/../../../../armv7a-unknown-linux-musleabihf/bin/ld: ../isc/libisc.a(backtrace.o): in function `btcallback':
backtrace.c:(.text+0x50): undefined reference to `_Unwind_GetIP'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:490: sample-async] Error 1
/usr/lib/gcc/armv7a-unknown-linux-musleabihf/10.3.0/../../../../armv7a-unknown-linux-musleabihf/bin/ld: ../isc/libisc.a(backtrace.o): in function `btcallback':
backtrace.c:(.text+0x50): undefined reference to `_Unwind_GetIP'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:486: resolve] Error 1
I think this is related to this change here:
--- /var/tmp/portage/net-dns/bind-tools-9.16.9/work/bind-9.16.9/lib/isc/backtrace.c 2020-11-16 14:44:37.000000000 +0000
+++ /var/tmp/portage/net-dns/bind-tools-9.16.8/work/bind-9.16.8/lib/isc/backtrace.c 2020-10-13 08:41:40.000000000 +0000
@@ -40,7 +40,7 @@
*/
#ifdef HAVE_LIBCTRACE
#define BACKTRACE_LIBC
-#elif defined(HAVE_UNWIND_BACKTRACE)
+#elif defined(__GNUC__) && (defined(__x86_64__) || defined(__ia64__))
#define BACKTRACE_GCC
#elif defined(WIN32)
#define BACKTRACE_WIN32
If I revert this change then my compile succeeds (although it may not be correct?)
I'm not really skilled enough to understand the details of gcc backtrace implementation on arm. I'm using gcc 10.3.0 to compile this, and I can see that I have a header:
/usr/lib/gcc/armv7a-unknown-linux-musleabihf/10.3.0/include/unwind.h
So I'm assuming that I have gcc compiled with some kind of unwind implementation?
I use a very similar profile to compile near identical code base for both amd64 and x86 architectures and both of those have no issues compiling latest bind-tools (and previous). Also, near as I can see I have my gcc configured identically across all three systems...
Now I *can* compile bind-tools ok if I install the libunwind library, however, that then breaks (re)compiling my gcc compiler, so I'm really thinking that's the wrong route to go down?
Temporarily I'm reverting the above change locally, but I wonder if you could either guide me to a correct solution, or if someone more knowledgeable can revert or write some correct #if test for this situation please?
I'm sure I have failed to provide enough details at this stage. Please be gentle...Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2849Dig: Add option to change default record type2022-04-26T13:36:02ZSören KleinDig: Add option to change default record type### Description
It would be great to have the option to change the default record type from e.g. `A` to `AAAA`.
It would also be very helpful if multiple default record types are supported, e.g. `A, AAAA`.
### Request
I would like t...### Description
It would be great to have the option to change the default record type from e.g. `A` to `AAAA`.
It would also be very helpful if multiple default record types are supported, e.g. `A, AAAA`.
### Request
I would like to set the default records either with an option, e.g. `dig --set-default-records "A, AAAA"` or as part of an system environment variable.
If multiple record types are defined, then the command `dig example.com` with the types `A, AAAA` should be extended to `dig example.com A example.com AAAA`.
### Links / referencesNot plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2862Persistent mode doesn't work with `named` AFL fuzzing2022-04-02T07:50:35ZSiva Kesava R KakarlaPersistent mode doesn't work with `named` AFL fuzzing### Summary
When the code is compiled with `afl-clang-fast` to enable fuzzing of `named` in persistent mode, it either results in a compilation error with an older version (2.52b) or goes through with the latest version (3.14c), but the...### Summary
When the code is compiled with `afl-clang-fast` to enable fuzzing of `named` in persistent mode, it either results in a compilation error with an older version (2.52b) or goes through with the latest version (3.14c), but the persistent mode is not detected.
### BIND version used
Older version:
- BIND 9.17.5 (Development Release) <id:dbcf683>
- afl-clang-fast 2.52b
- clang version 4.0.1-10 (tags/RELEASE_401/final)
- Ubuntu:bionic container; afl-clang-fast installed with `apt install afl++`
Latest Version:
- BIND 9.17.16 (Development Release) <id:502f48a>
- afl-cc ++3.14c, mode: LLVM-PCGUARD [(afl-clang-fast symlinks to afl-cc and uses the mode variable to detect LLVM or gcc)](https://github.com/AFLplusplus/AFLplusplus#a-selecting-the-best-afl-compiler-for-instrumenting-the-target)
- Ubuntu clang version 12.0.1-++20210630032618+fed41342a82f-1~exp1~20210630133332.127
- Using aflplusplus/aflplusplus:latest container
### Steps to reproduce
Older version:
- cd bind9; `autoreconf -fi`
- `CXX=afl-clang-fast++ CC=afl-clang-fast ./configure --enable-fuzzing=afl --disable-linux-caps --disable-shared --enable-static --enable-developer --without-cmocka --without-zlib`
- `make -j`
The above `make` results in the following error:
```
make[4]: Entering directory '/bind9/bin/named'
CC fuzz.o
afl-clang-fast 2.52b by <lszekeres@google.com>
fuzz.c:585:2: error: cast from 'const char *' to 'char *' drops const qualifier [-Werror,-Wcast-qual]
__AFL_LOOP(0);
^
<command line>:11:88: note: expanded from here
#define __AFL_LOOP(_A) ({ static volatile char *_B __attribute__((used)); _B = (char*)"##SIG_AFL_PERS...
^
1 error generated.
```
Commenting out that [line from `fuzz.c`](https://gitlab.isc.org/isc-projects/bind9/-/blob/dbcf683c1a57f49876e329fca183cb39d20ca3a4/bin/named/fuzz.c#L577) makes without any issue, but AFL doesn’t recognize it to be in persistent mode (expected as this line was used to signal that).
The build goes through if `afl-clang` is used instead of the `afl-clang-fast`. The problem is that `named` has to be fuzzed in persistent mode only: there is a check for if the environment variable [`AFL_Persistent` is set in fuzz.c](https://gitlab.isc.org/isc-projects/bind9/-/blob/dbcf683c1a57f49876e329fca183cb39d20ca3a4/bin/named/fuzz.c#L752 ) and then it spawns a new fuzz thread.
Latest Version:
Everything gets built using the same above commands, but the new thread is not spawned when run as the above check fails. Running `named -A client:127.0.0.1:53 -g` actually results in a segmentation fault (printing `...found 8 CPUs, using 8 worker threads; using 8 UDP listeners per interface; segmentation fault`) when compiled with the latest version of afl++.
----------------
What version combination (Bind version + clang version) works well for fuzzing the `named` binary using the `-A client:127.0.0.1:53` argument? Are there some flags that have to be set to allow the detection of the persistent mode and allows fuzz thread spawning in the `named_fuzz_setup` function?Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2865Follow-up from "Test migrating CSK to dnssec-policy"2021-08-17T14:52:13ZMatthijs Mekkingmatthijs@isc.orgFollow-up from "Test migrating CSK to dnssec-policy"The following discussion from !5328 should be addressed:
- [ ] @marka started a [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5328#note_230211): (+2 comments)
> I would test migrating 2 SEP keys. I would...The following discussion from !5328 should be addressed:
- [ ] @marka started a [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5328#note_230211): (+2 comments)
> I would test migrating 2 SEP keys. I would also test migrating 2 non-SEP keys.Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2876upgrade tests for persistent data are missing2021-08-26T20:32:47ZPetr Špačekpspacek@isc.orgupgrade tests for persistent data are missingWe need tests to cover compatibility of persistent files between versions. List of formats which come to mind:
- [ ] zone journal
- [ ] zone in raw format
- [ ] zone in map format
- [ ] new-zone database (NZD) in our custom format
- [ ] ...We need tests to cover compatibility of persistent files between versions. List of formats which come to mind:
- [ ] zone journal
- [ ] zone in raw format
- [ ] zone in map format
- [ ] new-zone database (NZD) in our custom format
- [ ] new-zone database (NZD) in LMDB
- [ ] managed-keys
This list might not be exhaustive.Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2879Add --disable-doh to a CI build?2023-11-02T16:26:08ZMark AndrewsAdd --disable-doh to a CI build?The following discussion from !5353 should be addressed:
- [ ] @marka started a [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5353#note_231504): (+1 comment)
> One remaining question is "do we add yet ano...The following discussion from !5353 should be addressed:
- [ ] @marka started a [discussion](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/5353#note_231504): (+1 comment)
> One remaining question is "do we add yet another system with --disable-doh to CI?"
- [ ] Also should we have a CI build that does not have libnghttp2 installed.Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2883Let name of inline-signed zone file be configured2023-11-02T16:26:08ZMagnus HolmgrenLet name of inline-signed zone file be configured### Description
The names of journal files can be overridden (with `journal`), but not the names of the signed zone files created when `inline-signing=yes`. They are always named like the original file with `.signed` appended. https://g...### Description
The names of journal files can be overridden (with `journal`), but not the names of the signed zone files created when `inline-signing=yes`. They are always named like the original file with `.signed` appended. https://gitlab.isc.org/isc-projects/bind9/-/blob/2872d6a12efe578360a641c1ba90884ea9a7dd01/bin/named/zoneconf.c#L1116
It's not a huge deal, but I'd like to separate manually edited configuration from software managed data per the FHS, and thus keep non-dynamic master zones in /etc (which is also what the Debian package recommends) but the inline-signed zone data in /var/lib. (It appears that the Debian BIND maintainers didn't consider inline signing, because the included AppArmor profile prevents `named` from writing to /etc/bind.)
### Request
Define a new option `signed-file` or similar. Could something like [signed-file.patch](/uploads/ec5f66b98f5c986d867ea76ccc4a89d9/signed-file.patch) work?Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2892The Umbrella EDNS option has been published by IANA2021-09-13T20:37:12ZMark AndrewsThe Umbrella EDNS option has been published by IANA```
20292 Umbrella Ident Optional [https://developer.cisco.com/docs/cloud-security/#!integrating-network-devices/rdata-description][Cisco_CIE_DNS_team]
```
- Add the ability to check and display the option contents
- Add support to +edn...```
20292 Umbrella Ident Optional [https://developer.cisco.com/docs/cloud-security/#!integrating-network-devices/rdata-description][Cisco_CIE_DNS_team]
```
- Add the ability to check and display the option contents
- Add support to +ednsopt in dig.Not plannedhttps://gitlab.isc.org/isc-projects/bind9/-/issues/2915False positive with CVE-2020-8622 regression test2022-04-07T13:14:12ZMark AndrewsFalse positive with CVE-2020-8622 regression testIf the timeout for between successive queries has been shortened for
```
I:tsig:check that a malformed truncated response to a TSIG query is handled
```
the test can fail. The default is +time=5, if it is set to 1 (e.g. via .digrc)
na...If the timeout for between successive queries has been shortened for
```
I:tsig:check that a malformed truncated response to a TSIG query is handled
```
the test can fail. The default is +time=5, if it is set to 1 (e.g. via .digrc)
named is still performing lookups when dig times out.Not plannedMark AndrewsMark Andrews