Not had time to look into why but just updating from 1.8.1 to 1.8.2 means that DNS names do not get resolved.
Will look into it when I have a bit of time.
Not had time to look into why but just updating from 1.8.1 to 1.8.2 means that DNS names do not get resolved.
Will look into it when I have a bit of time.
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
Better show your config.
PS. 1.8.2 win64 run smoothly on my Win10 x64 with same config as 1.8.1.
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.
Yes,
a lot of timeouts:
04/12/2018 16:52:09 C:\Program Files\Unbound\unbound.exe[5484:1] debug: query response was timeout
Seems firewall blocked changed binary access to internet.
OK it is now resolved.
I have no idea what happened but somehow the AV got itself all messed up and when I logged in as administrator It suddenly popped up, decided it was broken and then uninstalled and re-installed itself. This was followed by yet another update.
So it seems it was just a coincidence that what ever happened, happened and 1.8.2 did not work whereas 1.8.1 did I tried going back and forth between the two versions several times and it was always the same 1.8.1 worked 1.8.2 did not.
However I am now running 1.8.2 with no issues. ![]()
Ray