Thanks. I was able to restore the source-built 9.18 version I had built but then deleted when I moved to MacPorts and it has the same behavior so a BIND 9.18 issue and nothing to do with MacPorts. I’ll post about it in the BIND mailing list.
-- Larry Stone [email protected] > On Jun 26, 2022, at 10:18 AM, Daniel J. Luke <[email protected]> wrote: > > The bind9 port doesn't patch this behavior (if you look at the port, there's > a configure patch because upstream uses broken glibtool and an atomics patch > to allow building w/ older clang versions), so it's almost certainly due to > an upstream change. > >> On Jun 26, 2022, at 8:23 AM, Larry Stone <[email protected]> wrote: >> Good observation. Still, what the MacPorts version of dig is doing is not >> the default (or at least hasn’t been (see next paragraph) as I mentioned in >> my first post, I used to build BIND from source). >> >> But one other thought I just had is it’s a change with the latest version of >> BIND. The Apple provided dig is old enough that it must be BIND 9.16 and the >> source-built version I tested with is also from the 9.16 tree. But the >> MacPorts version is from the new 9.18 tree. Unfortunately, I no longer have >> a source-built 9.18 copy of dig to test with. > > -- > Daniel J. Luke >
