Secure DNS not working!

Keep getting the message from avast “Secure DNS can’t run on this network”.

Here is the contents of my SecureDns.log:
[2014/11/11 07:39:16.848,3304] SecureDNS[?]: [NOTICE] Voting started…
[2014/11/11 07:39:17.659,656] SecureDNS[0]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:17.659,656] SecureDNS[0]: [INFO] Initializing libsodium for optimal performance
[2014/11/11 07:39:17.706,656] SecureDNS[0]: [INFO] Generating a new key pair
[2014/11/11 07:39:17.737,656] SecureDNS[0]: [INFO] Done
[2014/11/11 07:39:17.815,656] SecureDNS[0]: [NOTICE] Engine initialization for “avast_sin03.ff.avast.com_443” is complete
[2014/11/11 07:39:17.815,656] SecureDNS[0]: [NOTICE] TCP listener port: 49168
[2014/11/11 07:39:17.815,656] SecureDNS[0]: [NOTICE] UDP listener port: 55544
[2014/11/11 07:39:17.847,3392] SecureDNS[1]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:17.847,3392] SecureDNS[1]: [INFO] Generating a new key pair
[2014/11/11 07:39:17.847,3392] SecureDNS[1]: [INFO] Done
[2014/11/11 07:39:17.878,3392] SecureDNS[1]: [NOTICE] Engine initialization for “avast_ams11.ff.avast.com_443” is complete
[2014/11/11 07:39:17.878,3392] SecureDNS[1]: [NOTICE] TCP listener port: 49172
[2014/11/11 07:39:17.878,3392] SecureDNS[1]: [NOTICE] UDP listener port: 55546
[2014/11/11 07:39:17.893,3396] SecureDNS[2]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:17.893,3396] SecureDNS[2]: [INFO] Generating a new key pair
[2014/11/11 07:39:17.893,3396] SecureDNS[2]: [INFO] Done
[2014/11/11 07:39:17.925,3392] SecureDNS[1]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:17.925,3392] SecureDNS[1]: [INFO] This certificate looks valid
[2014/11/11 07:39:17.925,3392] SecureDNS[1]: [INFO] Server key fingerprint is C74F:F1A4:9D97:9E4C:D5C6:4FA9:0D8D:3D7C:7603:C048:1755:90B1:EB83:FB6F:0957:E224
[2014/11/11 07:39:17.925,3392] SecureDNS[1]: [NOTICE] Proxying from 127.0.0.1:0 to 159.253.145.176:443
[2014/11/11 07:39:17.925,3396] SecureDNS[2]: [NOTICE] Engine initialization for “avast_sin03.ff.avast.com_53” is complete
[2014/11/11 07:39:17.925,3396] SecureDNS[2]: [NOTICE] TCP listener port: 49175
[2014/11/11 07:39:17.925,3396] SecureDNS[2]: [NOTICE] UDP listener port: 55548
[2014/11/11 07:39:17.971,3400] SecureDNS[3]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:17.971,3400] SecureDNS[3]: [INFO] Generating a new key pair
[2014/11/11 07:39:17.971,3400] SecureDNS[3]: [INFO] Done
[2014/11/11 07:39:17.987,3392] SecureDNS[1]: [INFO] DNS_Sec Answer [id=1944:1944, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.02
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:17.987,3400] SecureDNS[3]: [NOTICE] Engine initialization for “avast_mia11.ff.avast.com_53” is complete
[2014/11/11 07:39:18.003,3400] SecureDNS[3]: [NOTICE] TCP listener port: 49178
[2014/11/11 07:39:18.003,3400] SecureDNS[3]: [NOTICE] UDP listener port: 55551
[2014/11/11 07:39:18.018,3404] SecureDNS[4]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:18.018,3404] SecureDNS[4]: [INFO] Generating a new key pair
[2014/11/11 07:39:18.018,3404] SecureDNS[4]: [INFO] Done
[2014/11/11 07:39:18.049,3304] SecureDNS[1]: [NOTICE] Measured PING time: 53, load: 2
[2014/11/11 07:39:18.049,3404] SecureDNS[4]: [NOTICE] Engine initialization for “avast_sin04.ff.avast.com_443” is complete
[2014/11/11 07:39:18.049,3404] SecureDNS[4]: [NOTICE] TCP listener port: 49181
[2014/11/11 07:39:18.049,3404] SecureDNS[4]: [NOTICE] UDP listener port: 55553
[2014/11/11 07:39:18.081,3388] SecureDNS[5]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:18.081,3388] SecureDNS[5]: [INFO] Generating a new key pair
[2014/11/11 07:39:18.081,3388] SecureDNS[5]: [INFO] Done
[2014/11/11 07:39:18.112,3388] SecureDNS[5]: [NOTICE] Engine initialization for “avast_ams01-037.ff.avast.com_53” is complete
[2014/11/11 07:39:18.112,3388] SecureDNS[5]: [NOTICE] TCP listener port: 49184
[2014/11/11 07:39:18.112,3388] SecureDNS[5]: [NOTICE] UDP listener port: 55556
[2014/11/11 07:39:18.127,3384] SecureDNS[6]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:18.127,3384] SecureDNS[6]: [INFO] Generating a new key pair
[2014/11/11 07:39:18.127,3384] SecureDNS[6]: [INFO] Done
[2014/11/11 07:39:18.159,3384] SecureDNS[6]: [NOTICE] Engine initialization for “avast_sin04.ff.avast.com_53” is complete
[2014/11/11 07:39:18.159,3384] SecureDNS[6]: [NOTICE] TCP listener port: 49187
[2014/11/11 07:39:18.159,3384] SecureDNS[6]: [NOTICE] UDP listener port: 55558
[2014/11/11 07:39:18.159,3388] SecureDNS[5]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.159,3388] SecureDNS[5]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.159,3388] SecureDNS[5]: [INFO] Server key fingerprint is DE2F:E2FC:861A:E90D:7C20:1950:6E4B:B561:07CB:7B90:F0AF:BCAE:F664:A955:9291:6F1C
[2014/11/11 07:39:18.159,3400] SecureDNS[3]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.159,3400] SecureDNS[3]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.159,3400] SecureDNS[3]: [INFO] Server key fingerprint is F98F:A41A:0514:D234:C56C:E8EE:13DC:0492:280E:8D20:2F66:D450:0BF7:DD7E:100B:2E11
[2014/11/11 07:39:18.159,3388] SecureDNS[5]: [NOTICE] Proxying from 127.0.0.1:0 to 5.45.62.77:53
[2014/11/11 07:39:18.159,3400] SecureDNS[3]: [NOTICE] Proxying from 127.0.0.1:0 to 77.234.42.87:53
[2014/11/11 07:39:18.174,3376] SecureDNS[7]: [NOTICE] Starting dnscrypt-proxy 1.4.0
[2014/11/11 07:39:18.174,3376] SecureDNS[7]: [INFO] Generating a new key pair
[2014/11/11 07:39:18.190,3376] SecureDNS[7]: [INFO] Done
[2014/11/11 07:39:18.205,3376] SecureDNS[7]: [NOTICE] Engine initialization for “avast_dal05.ff.avast.com_443” is complete
[2014/11/11 07:39:18.205,3376] SecureDNS[7]: [NOTICE] TCP listener port: 49190
[2014/11/11 07:39:18.205,3376] SecureDNS[7]: [NOTICE] UDP listener port: 55560
[2014/11/11 07:39:18.221,656] SecureDNS[0]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.221,656] SecureDNS[0]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.221,656] SecureDNS[0]: [INFO] Server key fingerprint is 17B1:BD0D:C543:4F52:9A0D:1BC4:EC25:2C08:41BB:1D8A:8DA1:A9F6:0E04:308E:D782:DD27
[2014/11/11 07:39:18.221,656] SecureDNS[0]: [NOTICE] Proxying from 127.0.0.1:0 to 216.185.103.158:443
[2014/11/11 07:39:18.315,3388] SecureDNS[5]: [INFO] DNS_Sec Answer [id=1944:3, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.00
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:18.330,3396] SecureDNS[2]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.330,3396] SecureDNS[2]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.330,3396] SecureDNS[2]: [INFO] Server key fingerprint is 17B1:BD0D:C543:4F52:9A0D:1BC4:EC25:2C08:41BB:1D8A:8DA1:A9F6:0E04:308E:D782:DD27
[2014/11/11 07:39:18.330,3396] SecureDNS[2]: [NOTICE] Proxying from 127.0.0.1:0 to 216.185.103.158:53
[2014/11/11 07:39:18.346,3376] SecureDNS[7]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.346,3376] SecureDNS[7]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.346,3376] SecureDNS[7]: [INFO] Server key fingerprint is C83E:575B:B022:1281:1A19:C67C:29BE:54A5:7839:5EAB:AC35:DCD9:0D7E:66D7:0230:FA46
[2014/11/11 07:39:18.361,3376] SecureDNS[7]: [NOTICE] Proxying from 127.0.0.1:0 to 67.228.177.241:443
[2014/11/11 07:39:18.377,3304] SecureDNS[5]: [NOTICE] Measured PING time: 54, load: 0
[2014/11/11 07:39:18.424,3404] SecureDNS[4]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.424,3404] SecureDNS[4]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.424,3404] SecureDNS[4]: [INFO] Server key fingerprint is 9FB7:82E5:4716:5FD5:7833:E856:3CE1:11C3:503D:9392:344A:9D5A:B91D:4157:DFF1:F906
[2014/11/11 07:39:18.424,3404] SecureDNS[4]: [NOTICE] Proxying from 127.0.0.1:0 to 216.185.103.154:443
[2014/11/11 07:39:18.424,3400] SecureDNS[3]: [INFO] DNS_Sec Answer [id=1944:2, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.09
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:18.486,3304] SecureDNS[3]: [NOTICE] Measured PING time: 167, load: 9
[2014/11/11 07:39:18.533,3384] SecureDNS[6]: [INFO] Server certificate #808464433 received
[2014/11/11 07:39:18.533,3384] SecureDNS[6]: [INFO] This certificate looks valid
[2014/11/11 07:39:18.533,3384] SecureDNS[6]: [INFO] Server key fingerprint is 9FB7:82E5:4716:5FD5:7833:E856:3CE1:11C3:503D:9392:344A:9D5A:B91D:4157:DFF1:F906
[2014/11/11 07:39:18.533,3384] SecureDNS[6]: [NOTICE] Proxying from 127.0.0.1:0 to 216.185.103.154:53
[2014/11/11 07:39:18.549,3376] SecureDNS[7]: [INFO] DNS_Sec Answer [id=1944:5, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.01
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:18.595,3304] SecureDNS[7]: [NOTICE] Measured PING time: 172, load: 1
[2014/11/11 07:39:18.642,656] SecureDNS[0]: [INFO] DNS_Sec Answer [id=1944:1, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.01
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:18.767,3304] SecureDNS[0]: [NOTICE] Measured PING time: 390, load: 1
[2014/11/11 07:39:18.783,3396] SecureDNS[2]: [INFO] DNS_Sec Answer [id=1944:4, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.01
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:18.845,3404] SecureDNS[4]: [INFO] DNS_Sec Answer [id=1944:6, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.01
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:18.876,3304] SecureDNS[2]: [NOTICE] Measured PING time: 416, load: 1
[2014/11/11 07:39:18.876,3304] SecureDNS[4]: [NOTICE] Measured PING time: 371, load: 1
[2014/11/11 07:39:18.939,3384] SecureDNS[6]: [INFO] DNS_Sec Answer [id=1944:7, proto=17] (RESPONSE) with 1 queries and 2 answers
DNS Query (kind 2 type 16 TXT) load.securedns.avast.com
DNS Answer kind 10 type 16 TXT TXT_REC load.securedns.avast.com → 0.01
DNS Answer kind 0 type 41 EDNS Dump not available for name “”
[2014/11/11 07:39:19.001,3304] SecureDNS[6]: [NOTICE] Measured PING time: 358, load: 1
[2014/11/11 07:39:28.065,3304] SecureDNS[1]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:28.392,3304] SecureDNS[5]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:28.501,3304] SecureDNS[3]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:28.720,3304] SecureDNS[7]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:28.829,3304] SecureDNS[0]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:28.938,3304] SecureDNS[2]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:28.938,3304] SecureDNS[4]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:39:29.047,3304] SecureDNS[6]: [WARNING] Thread_Kill Timeout
[2014/11/11 07:47:45.410,3216] SecureDNS[?]: [INFO] Counters: Requests=000111 Resend=000000 ResponsesOrg=000100 ResponsesSec=000008
[2014/11/11 08:38:18.142,3212] SecureDNS[?]: [INFO] Counters: Requests=000212 Resend=000000 ResponsesOrg=000200 ResponsesSec=000008
[2014/11/11 08:44:58.216,3212] SecureDNS[?]: [INFO] Counters: Requests=000314 Resend=000000 ResponsesOrg=000300 ResponsesSec=000008

Best regards,
Kenneth3

Hi Kenito,
thanks for log. It looks as localhost interprocess communication is blocked for some reason on your computer. Do you have any firewall (Avast Firewall) installed?

Yes, I have ZoneAlarm Pro. In the Advanced Settings I have the “Lock hosts file” checked.
Should I unchecked this “Lock hosts file” option?

Thanks,
Kenito.

You can try it, but hosts file is different thing than localhost communication. Please try to find settings or firewall rule for IP addresses beginning by number 127. These addresses are called localhost or sometimes IP loopback.
Probably, adding firewall rule for address 127.0.0.0, mask 255.0.0.0 and avast! service process will be necessary.

We will test your combination of Avast and ZoneAlarm