search for: resolver_unbound

Thanks, I did enable debugging but didn't see any attempts to resolve hostnames. I will give it another look. I did have an empty resolver_unbound.conf (not even a general context) - would that likely cause issues? I would expect the defaults to kick in but I have now added: [general] hosts=system I will retest/debug when ASAP. Mark. On Thu, 4 Apr 2019 at 15:20, Joshua C. Colp <jcolp at digium.com> wrote: > On Thu, Apr 4, 2019...

Seems to be res_resolver_unbound.so Reading the documentation now but any hints greatly appreciated! Mark. On Thu, 4 Apr 2019 at 15:07, Joshua C. Colp <jcolp at digium.com> wrote: > On Thu, Apr 4, 2019, at 11:03 AM, Mark Farmer wrote: > > Sorry, should have included that. > > > > Asterisk 16.2.1 &gt...

...r 2019 at 15:30, Joshua C. Colp <jcolp at digium.com> wrote: > On Thu, Apr 4, 2019, at 11:27 AM, Mark Farmer wrote: > > Thanks, I did enable debugging but didn't see any attempts to resolve > > hostnames. I will give it another look. > > > > I did have an empty resolver_unbound.conf (not even a general context) > > - would that likely cause issues? I would expect the defaults to kick > > in but I have now added: > > > > [general] > > hosts=system > > > > I will retest/debug when ASAP. > > The default would have indeed kicked...