pfSense » pfSense Plus

We are using the Nexus/Threatgate solution integrated into pfSense Plus.
The forwarding engine performs a strict, case-sensitive comparison between the incoming query and the zone defined in the configuration. If a client sends a query containing uppercase letters, the forward rule is completely ignored.
Observed Technical Behavior:

• Our forward directive is configured for the local domain: forward mydomain.local via 192.168.200.4:53.
• In an Active Directory environment, Windows clients natively send queries with uppercase letters due to their Primary DNS Suffix (e.g., myprinterserver. MYDOMAIN .local) or during SMB requests (e.g., \\MYPRINTERSERVER).
  Faced with a query containing uppercase characters, rexdns refuses to forward the request to the local Domain Controller (192.168.200.4).
  According to our packet captures (tcpdump), the Nexus DNS service stalls for a timeout of exactly 2 seconds, then returns a ServFail packet to the client.

GUI Limitation:
To bypass this engine bug, we attempted to add a static resolve or forward rule including the uppercase letters. However, the Nexus web GUI strictly prohibits the input of uppercase characters in these fields. It is therefore impossible for an administrator to work around the rexdns engine flaw via the UI.

Since the DNS protocol is by definition case-insensitive (Domain Name System Case Insensitivity Clarification - RFC 4343), would it be possble to:

• Make the rexdns plugin fully case-insensitive when evaluating rules (the standard expected behavior of any DNS server).
• Or at the very least, allow uppercase input in the management GUI to let administrators create workaround rules.

Thank you in advance for looking into this issue.