Hotfix-1176 for Release 10.5.1 (SE)

Power supply unit (PSU) sensors on F1000b appliances are now monitored correctly, so PSU status and health are reported as expected. BNNGF-102381

Firewalls now report a clean release state after an additional SSD is enabled, because the log directory keeps its correct permissions and group ownership when its storage is moved to the SSD. [BNNGF-102229]

F600d and F600e appliances now correctly detect their SFP port layout, so the right interface configuration is applied and all interfaces appear in Firewall Admin. [BNNGF-102457]

Firewalls that use DNS-based (hostname) network objects or custom DNS applications now maintain stable memory and CPU usage over time, avoiding a gradual memory increase and raised CPU load during DNS refresh handling. [BNNGF-102135]

DNS name resolution now works reliably for clients behind the firewall when DNS filtering or URL categorization is enabled, resolving intermittent lookup failures caused by a small fraction of DNS responses being dropped. [BNNGF-102521]

Firewalls that use DNS-based (hostname) network objects or custom DNS applications now remain stable under concurrent DNS activity, preventing a rare timing-related crash in the DNS resolution engine. [BNNGF-101730]

The secondary unit of an HA cluster now stays responsive under heavy source-NAT port usage, preventing the firewall engine soft lockups that could previously make the unit unreachable in Firewall Admin.[BNNGF-101765], [BNNGF-102401]

Remote access (RAC) ACL policies are now enforced when each session is created, so SecureEdge Access users can only reach protected resources permitted by the current policy — including after re-authentication expiry, policy changes, or security-posture denials. [BNNGF-102226]

On SecureEdge, disabling the web filter through a Device Profile or a per-user override now takes effect correctly, so URL filtering is no longer enforced for the affected users. [BNNGF-]102543

SecureEdge remote-access connections to applications identified by hostname (such as internal ZTNA web apps) are now permitted by their matching access rule instead of being incorrectly blocked after updating to 10.5.1. [BNNGF-102571]

Firewalls with multiple firewall services configured now keep URL filtering and DNS resolution working, resolving a startup failure of the URL categorization service that could occur when more than one service was present. [BNNGF-102596]

The firewall now returns both IPv4 and IPv6 DNS responses reliably while URL categorization is in progress, so clients no longer experience intermittent DNS timeouts for newly seen domains. [BNNGF-102603]

DNS lookups that are served by the firewall's local DNS cache are now returned reliably while URL categorization is active, resolving occasional missing responses that could cause client DNS timeouts. [BNNGF-102633]