Zenarmor 2.2 Review: Enterprise DNS Enhancements & OPNsense Compatibility

What Is Zenarmor? (Overview)

Zenarmor is a software-only next-generation firewall (NGFW) and SASE-aligned security platform designed to run on standard hardware, virtual machines, cloud infrastructure, and endpoints. Unlike proprietary appliances, Zenarmor emphasizes:

• Application-aware and identity-aware traffic control

• Deep inspection of encrypted traffic

• Cloud-driven threat intelligence

• Flexible deployment across gateways, endpoints, and private networks

Zenarmor is commonly deployed alongside OPNsense firewalls but is not limited to a single platform or topology.

What’s New in Zenarmor 2.2

Zenarmor 2.2 focuses on enterprise integration, stability, and private networking. While it includes multiple usability and reliability improvements, its most significant enhancement is expanded DNS integration for secure private networks, officially announced by Zenarmor.

Expanded DNS Integration for Secure Private Networks

In Zenarmor Secure Private Networks, peers (gateways and endpoints) are automatically registered into Zenarmor’s DNS infrastructure to enable discovery, monitoring, and policy enforcement. Zenarmor 2.2 expands this capability by allowing administrators to define:

• Custom DNS servers (e.g., internal or Active Directory DNS)

• Custom DNS search domains

• Coexistence with Zenarmor-managed peer DNS namespaces

This enhancement enables seamless integration with enterprise DNS architectures, hybrid cloud environments, and multi-domain networks—without sacrificing visibility or control.

Enterprise Impact:

• Improved interoperability with existing DNS and directory services

• Centralized DNS configuration distributed automatically to peers

• Reduced operational complexity in hybrid environments

• Better control over internal name resolution and privacy

Stability, Policy, and UI Improvements

Zenarmor 2.2 also includes:

• Improved handling of license changes and policy exemptions

• Refinements to reporting defaults and analytics behavior

• UI fixes for dashboards, filters, and scheduled reports

• Stability improvements for long-running gateways and constrained systems

These changes improve reliability and reduce administrative friction in production deployments.

Core Zenarmor Capabilities (Unchanged)

Deployment Flexibility

Zenarmor remains fully appliance-independent, supporting:

• On-premises gateways

• Virtual and cloud firewalls

• Branch and edge deployments

• Endpoints and secure private overlay networks

This allows organizations to scale security without redesigning infrastructure.

Editions & Licensing

Zenarmor is available in multiple editions, including Free, Home, Business NGFW, and SSE/SASE tiers. Feature availability (such as TLS inspection and private networking) depends on license level.

Zenarmor 2.2 – OPNsense Compatibility (Vendor-Safe Statement)

This section documents officially supported compatibility only, based strictly on vendor documentation and supported platform statements.

Officially Supported OPNsense Versions

Support Conditions

Zenarmor 2.2 support applies only when:

• OPNsense 24.7 or stable 25.x is used

• Compatible Zenarmor plugins are installed

• Vendor-documented installation and upgrade procedures are followed

Deployments outside these conditions fall outside official support scope.

Conclusion

Zenarmor 2.2 represents a meaningful step toward enterprise-grade secure private networking, particularly through its expanded DNS integration. Combined with improved stability and officially supported OPNsense platforms, it offers organizations a flexible, software-based alternative to traditional firewall appliances—without compromising control or visibility.

For environments requiring vendor backing and audit readiness, Zenarmor 2.2 on supported OPNsense versions provides a solid and defensible security foundation.

Appendix A: Operational Notes (Non-Support Guidance)

"Note: The following notes are provided for operational awareness only. They are not statements of official vendor support and should not be interpreted as certification or endorsement."

• Zenarmor relies on exclusive access to the Netmap packet engine per interface; other deep-inspection tools should not share the same interface.

• Zenarmor-protected interfaces should use MTU ≤ 1500 bytes.

• Hardware capacity (CPU/RAM) must be sized appropriately for TLS inspection and file scanning features.

• After major OPNsense upgrades, reporting databases may require re-initialization depending on deployment design.

• Newer or intermediate OPNsense builds may function but are not considered vendor-validated unless explicitly listed as supported.

These considerations are common to software-based NGFW deployments and should be evaluated during design and testing phases.

-->>>Get Started for Free<<<--

Official References

• Zenarmor 2.2 DNS Integration Announcement
  https://www.zenarmor.com/blog/zenarmor-2-2-expands-dns-integration-for-secure-private-networks

• Zenarmor Release Notes
  https://www.zenarmor.com/docs/support/release-notes

• Zenarmor OPNsense Installation Guide
  https://www.zenarmor.com/docs/opnsense