Hi Eli,
Your configuration looks correct (see the latets reference manual[1]),
but BIND 9.18 does not support forwarding queries via DoT. This feature
was introduced[2] in the development version of BIND 9 (9.19.10 and
later), and will be available in the next stable version of BIND 9.
[1]
> Wondering out loud:
> Maybe it should skip loading that particular member zone if the "coo"
> proproperty already points to different catalog? Would that be more
> resilient against race conditions when named is restarted?
That's an interesting suggestion, and I agree that it can solve the
> Interesting. I ended up just removing the TXT record but it is unclear
> why the zone entries would use that tsig labeled one instead of the
> globals since they were not referencing the tsig custom properties.
The labeled primaries have similar weight as the unlabled ones, and it's an
Hello, Jan-Piet,
> however, when I stop and restart the consumer server, I have sometimes (not
> always) seen
>
> catz: catz_addmodzone_cb: zone 'z10.aa' will not be added because another
> catalog zone already contains an entry with that zone
>
>which is true, but it doesn't _seem_ to
Hello, Gregory,
It looks like you are using a default labeled primary server without an IP
address, i.e. the TSIG key name is there for "tsig.primaries.ext", but the
A/ record for that name is missing:
> tsig.primaries.ext IN TXT "ns-gshapiro-net-xfer"
If your intention was to
That's good to hear, and thanks for the update.
All the best,
Aram
--
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
Hello Tom,
I see you are using BIND 9.18.9, can you retry with the latest version of BIND
9.18?
An issue, which looks similar to the one that you are experiencing, was fixed
in BIND 9.18.10, see https://gitlab.isc.org/isc-projects/bind9/-/issues/3638
Kind regards,
Aram
--
Visit
That's right, catalog zones are for synchronizing the list of zones served by
the primary, so that the secondaries can retrieve those zones using AXFR/IXFR.
You can't even use "allow-transfer" on a forward zone, so it is not meant to be
transferred to secondaries.
A couple of observations
8 matches
Mail list logo
