In message <caaiteh9-jqzw0fhlyx5eqc0s0hgw7snpo17akspav1ywbab...@mail.gmail.com> Matthew Pounsett <m...@conundrum.com> wrote:
>On Tue, 7 Sept 2021 at 03:45, Stephane Bortzmeyer <bortzme...@nic.fr> wrote: > >> The only solution is chasing the delegations from the root (which is >> what dig +trace is doing). Caching speeds it, this is why it is >> better to go through your resolver than using dig +trace. > >Yeah, you can pretty reliably get the answer in one or two steps by >requesting the NS set for the FQDN. You'll either get your answer, or >get an SOA with the name of the enclosing zone. Second lookup gets >you the NS set for the enclosing zone. Just using your local >recursive server to deal with tracking down the answer should work >well, unless for some reason you need to see every possible answer >from every delegating name server. I don't. And your other points are well taken. Having thought about the problem some more, I see now that you're probably right and that I should be able to code up something rather simple that will do the job if I put my mind to it. So thanks! Regards, rfg _______________________________________________ Please 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
