conorc 1 Posted January 15, 2021 Share Posted January 15, 2021 Hi, When we deploy this to anyone, their device can no longer resolve anthing. This is when they use the 'Obtain DNS server automatically' IPv4 setting on the Ethernet NIC. They have to use static DNS settings for it to work. When we roll back to 7.3.2044 it is resolved instantly, Thanks Link to comment Share on other sites More sharing options...
Administrators Marcos 4,710 Posted January 17, 2021 Administrators Share Posted January 17, 2021 Do you use default firewall settings, ie. automatic mode without any custom rules? Does actually pausing the firewall make a difference? Link to comment Share on other sites More sharing options...
itman 1,541 Posted January 17, 2021 Share Posted January 17, 2021 (edited) The way to diagnose this is as follows: 1. Set Ethernet IPv4 connection back to Obtain DNS server automatically. 2. Reboot device or do via command prompt window, ipconfig /flushdns, ipconfig /release, and ipconfig /renew commands to reset IPv4 connection and acquire a new IPv4 lease. 3. Via command prompt window, enter ipconfig /all and note IPv4 DNS server assignment IP addresses. 4. Open Eset GUI and then Network protection. 5. Select Advanced. Then select Zones -> Edit. In the DNS section, do you see the same IPv4 DNS server addresses noted in the prior ipconfig /all display? Edited January 17, 2021 by itman Link to comment Share on other sites More sharing options...
conorc 1 Posted January 19, 2021 Author Share Posted January 19, 2021 case closed. was a custom firewall rule in wrong order that never impacted us until DNS fallback was removed in version 8. thanks folks. Link to comment Share on other sites More sharing options...
Michelle911 0 Posted January 19, 2021 Share Posted January 19, 2021 Do you mind sharing what the custom rule is to maybe help someone else? Link to comment Share on other sites More sharing options...
Recommended Posts