AWS are aware of the issue and are just taking a long time to address it.
noted. pretty sure there's not a %*^$* thing i can do about THAT!
NXDOMAIN for ENTs can also be result of not adding delegating NS records to the parent zone when both parent and child zones are served by the same server. QNAME minimisation exposes lots of errors as it make queries that aren’t seen without it. The best way to do QNAME minimisation is to make NS queries as then you can cache non-existence of the NS RRset at intermediate nodes but then you run up against toy DNS servers / firewalls that only handle A and AAAA lookups.
atm, i'll read that as "use 'relaxed'". at least until i become aware of my next self-inflicted damage ;-) thx o/ -- 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://lists.isc.org/mailman/listinfo/bind-users
