Re: 9.18 BIND not iterated over all authoritative nameservers

> Am 30.10.2023 um 16:59 schrieb Michael Martinell via bind-users > : > > Thanks to all who responded. Putting qname-minimization disabled; in > named.conf resolves the issue in my testing. > > I did try specifying relaxed (which appears to be the default), but that > didn’t work either. >

Re: TLS Statistics

). Rainer -- 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

Re: DNSSEC adoption

Am 2022-08-03 15:27, schrieb Bob Harold: I think the best way to soften the effect, and make DNSSEC much less brittle, without losing any of the security, is to reduce the TTL of the DS record in the parent zone (usually TLD's) drastically - from 2 days to like 30 minutes. That allows quick

Re: Problem resolving a domain

Hi, Thanks for the hints! It does indeed work with these settings. The problem is also that google and quad9 and most of the rest of the internet seem to be able to resolve it. While I investigated this issue, I came around a posting from one or two years ago where similar problems with

Problem resolving a domain

Hi, at work, I have a problem resolving the following domain: myapplication.international.barclays.com BIND 9.16.27, FreeBSD 12.3-P5. 2022Q2 ports. I copied the config to a VM at home - but it did not work there, either. I believe it must have happened on the update from BIND 9.16.26 to