Our engineering team has identified the root cause and released a hotfix Windows client release (v2.1.1.0) addressing the DNS configuration issue identified in the prior release.
The hotfix automatically detects and corrects affected DNS settings upon startup, restoring internet connectivity and DNS functionality.
The updated client can be installed directly over the impacted version and includes all prior improvements and fixes from v2.1.0.0.
While initial assessment suggested some impacted endpoints might remain reachable via RMM, further validation confirms that RMM agents typically lose connectivity shortly after DNS failure, limiting remote remediation options.
Due to dependency on DNS resolution for standard deployment mechanisms, remote push/install via RMM is not expected to be viable in most cases.
We are actively evaluating alternative distribution methods that would allow customers to manually download and install the hotfix without relying on DNS. Any additional methods identified will be published as an update to this status page.
Our engineering team has identified the root cause and released a hotfix Windows client release (v2.1.1.0) addressing the DNS configuration issue identified in the prior release.
The hotfix automatically detects and corrects affected DNS settings upon startup, restoring internet connectivity and DNS functionality.
The updated client can be installed directly over the impacted version and includes all prior improvements and fixes from v2.1.0.0.
While initial assessment suggested some impacted endpoints might remain reachable via RMM, further validation confirms that RMM agents typically lose connectivity shortly after DNS failure, limiting remote remediation options.
Due to dependency on DNS resolution for standard deployment mechanisms, remote push/install via RMM is not expected to be viable in most cases.
We are actively evaluating alternative distribution methods that would allow customers to manually download and install the hotfix without relying on DNS. Any additional methods identified will be published as an update to this status page.
We are aware of a problem where the assignment of loopback DNS on local interfaces disrupts networking connections on version 2.1.0.0 of Datto Secure Edge.
The Kaseya R&D Team has identified the issue and is working towards a resolution.