I always manually configure the DNS server IP addresses for my network connections. Avast Free 19.7.2388 Wi-Fi Inspector now takes exception to my setting the OpenDNS IP addresses, 208.67.222.222 and 208.67.220.220.
This problem has only become apparent with Avast 19.7.2388. There seems to be no opportunity to overrule it.
Post a screenshot.
3 screenshots duly posted.
Might be a bug, wait for one of the devs and/or submit a ticket: https://support.avast.com/contact (paid versions)
This undermines the very valuable Wi-Fi Inspector facility. It worked reliably up to and including Avast 19.6.2383.
+1
Of the two cited addresses, I use only 208.67.222.222 as an alternate, and I get the same exception. I had to turn off my VPN to see it since when the VPN is connected, the TAP adapter substitutes a proprietary DNS server used by the VPN provider.
Side benefit to turning off the VPN was that Wi-Fi Inspector now recognizes/checks/verifies all the connected wireless entities, so I now know to include that step when I routinely run the Wi-Fi Inspector after an Avast update just to see whether Avast now sees anything differently in the network.
@loungehake, thanks for calling this out.
Hi guys, I forwarded it, let’s see…
following your web address 208.67.222.222
I get the following from Avast
https://screencast-o-matic.com/screenshots/u/Lh/1566136484689-74484.png
208.67.222.222. is an IP address used by OpenDNS. It is used by client computers which send DNS resolution requests to it via the UDP protocol to external port 53. I have used OpenDNS for many years for Internet domain name address resolution.
Yes it is one of the most famous DNS addresses, after google ( 8.8.8.8 )
The fact that avast online security detects something malicious doesn’t make sense since it’s not a website so this address doesn’t use Hypertext Transfer Protocol (port 80, 443 , …) , but a DNS protocol (port 53).
I wonder what AOS can see in it that is malicious… even to see something in it :-
On the other hand , AOS is not a firewall but a subjective tool for website analysis and it is well known when AOS sees a new site (lack of reputation), it warms, that’s what must happen here ?
What about 1.1.1.1 or 9.9.9.9 with AOS?
I found this evening that the same issue occurs with other versions of Avast. I was running a Wi-Fi scan on a friend’s Windows XP system running Avast 18.8 and the issue was there too. QED: it’s an error in the data supplied in the definitions updates, not a software bug.
Doesn’t Avast operate a white list of IP addresses and domain names of unquestionably high repute? This issue undermines all the good things in Avast and there are many. I attribute the use of OpenDNS as an important factor in my avoidance of malware and security incidents in nearly two decades of Internet use. This also applies to all the computers I look after for friends and family. I place the IP4 addresses 208.67.222.222 and 208.67.220.220 (and also, for good measure, the IP6 addresses 2620:119:35::35 and 2620:119:53::53) in the DNS properties of every network device of every computer that I maintain.
Hello,
thanks for reporting this issue, it should be already fixed.
Regards,
HK
I now get the following when using that address:
https://screencast-o-matic.com/screenshots/u/Lh/1566218519019-22862.png
Yes, this time it’s normal since this IP address is not a website, it was the previous message from AOS that was not
To convince yourself, try to open other DNS addresses such as google 8.8.8.8.–> same : “error connection timed out” 
On the other hand I confirm what HK says, the problem with the wifi-inspector is now solved if we use OpenDNS DNS (208.67.222.222)
Problem no longer exists. The Wi-Fi Inspector is an exellent feature and invaluable for auditing networks. It alerted me that the firmware in a D-Link wireless router (supplied by TalkTalk) was flawed and this led to the device being updated with modified firmware. Very useful.
I want a Wi-Fi inspector like Blakey in On The Buses. It should walk up and down saying “Tickets please” to network users.