sub-zone on the same server but in different backend - how?

Hi guys. To experts that most likely be silly easy but my brain got tangled up and cannot get around it now(also being a novice) Have a zone on a server, say: - the.zone with "flat" files being the backend for it. Now wanting to have: - sub.the.zone served by the same BIND server, but stor

Using NAT64 for IPv6 only DNS resolvers

Good morning, I was wondering whether it is possible to configure IPv6 only BIND resolvers to make use of a NAT64 prefix for outgoing requests? I.e. the following situation: - Resolver = 2001:db8::1, IPv6 only - NAT64 prefix = 2001:db8:1:c001::/96 Now if bind sees example.com NS a.b.c.d, can

Re: Using NAT64 for IPv6 only DNS resolvers

There is an open issue https://gitlab.isc.org/isc-projects/bind9/-/issues/608 and merge request https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/2166 to do this. That said you should be asking your OS vendors why they are not providing/enabling a CLAT implementation. You could also lo

Re: sub-zone on the same server but in different backend - how?

lejeczek via bind-users wrote: > > Have a zone on a server, say: > > - the.zone > > with "flat" files being the backend for it. Now wanting to have: > > - sub.the.zone > > served by the same BIND server, but stored in.. "SQL" backend. > > How... well how to make that work if at all possible? > I'd

AW: AXFR Problems sind Upgrade to 9.16.12

For the records. With the help of Ondrej we found the cause: The problem is related to TCP timeouts not working as expected. If you are affected set tcp-initial-timeout and tcp-idle-timeout to 1200 (=120s). If you have huge zones with AXFRs > 120s you can download the source, increase the max t