The log is riddled with

query response was timeout

Maybe a protective measure. firewall or ant-virus or some, on the OS that uses some checksum on the unbound.exe is preventing the new *.exe from connecting to the internet.

On 04.12.2018 18:26, RayG via Unbound-users wrote:

I have had to revert back to v1.8.1 as with the same configuration file v1.8.2 just does not want to resolve names. If it does it take an inordinate amount of time

 

Using Win 10 x64 V1809

 

I cannot see anything obvious in the log file. But then I am no expert…

 

A log file can be found here (16MB)

 

https://1drv.ms/u/s!As73rPtzISrUlm9DjQgFoob5olEI

 

Thanks for any suggestions.

 

Regards

Ray

 


Reply via email to