I've added some IPs to the allowed IPs Prevx can connect to, according to some older thread I've seen. But, I've been seeing Prevx being blocked a connection to 184.72.35.141. It has been working fine, though. Would it be recommended to add this one as well?
Yes, exactly. Prevx doesn't have a set range of IPs because of our global load balancing and randomization so you will need to allow access by DNS rather than IP to g*.prevxinfo.com. Let me know if you have any questions!
Which DNS? I mean, I have two rules for prevx.exe; one for DNS (the one I use) and one for the IPs I've seen mentioned in an older thread. Does Prevx make use of its own DNS? If so, which? -Edit- @ jmc777 Thank you for your feedback.
The DNS resolution for Prevx is highly dynamic and can change at any time so we strongly recommend not using the IPs resolving on your PC as a whitelist as it could block Prevx in the future. The most reliable way is just to allow through the mask of g*.prevxinfo.com
OK. I get it now. Just a slight problem, though. Windows Firewall lacks that option to add domains. One has got to live with what one has. lol
