A more concise DNS rule editor

[jiegengxiangjianxue]

The current visual DNS editing interface is too troublesome. It should be easier to use. Add a visual page for DNS rules and simplify the format of rule writing
For example:
Logic: or/and
Routing behavior: sniffing, hijacking DNS
Domain Name: xxxx
Domain name suffix: xxxx
Domain name keywords:
Domain name regular: xxxxx
App package ID: xxxxx
IP (CIDR): xx.xx.xx.xx (xx.xx.xx.xx/xx)
Port/port range: xx/x-xxxx
Network: UDP, TCP, icmp
Protocol: http, DNS, NTP, stun, TLS, QUIC, etc
This visual DNS rule would be extremely convenient，Also very suitable for Xiaobai
I hope developers can refer to this template (my hands are so tired).

[Leadaxe]

Thanks for the detailed template — and sorry your hands got tired typing it! 🙂

Good news: most of what you're asking for already exists in L×Box, just not in the DNS Settings screen. It lives in the routing rule editor (Custom Routing Rules → "+"), which has a full visual constructor with exactly the fields you listed:

• Domain (exact), Domain suffix, Domain keyword, IP CIDR — the MATCH section
• Port / Port range — the PORT section
• App package ID — the APPS section (app picker)
• Outbound / routing behavior — channel picker

The reason there is no separate constructor on the DNS page: in ~90% of real setups a DNS rule should follow its routing rule (same domains/apps → same channel → resolved by the same server). So instead of making you build the rule twice, the routing rule editor has a DNS section:

DNS → "Send DNS to dedicated server" → pick a DNS server

Turning that on makes the rule automatically register the matching DNS rule for you — no JSON, no duplicate entry. That's the visual DNS editing you're after; it's just reached through the routing rule rather than the DNS screen.

A standalone visual constructor inside the DNS Settings screen is not currently planned for this reason — the constructor already exists and DNS rides along with the routing rule.

A couple of honest caveats on your field list, due to sing-box limitations (not ours):

• Domain regex — supported by sing-box but not yet surfaced in the visual form; for now it needs the raw JSON entry.
• Protocol (http/dns/ntp/stun/tls/quic…) and Network (tcp/udp) — these are not evaluated for DNS rules built from a headless rule-set in sing-box, so a DNS rule can't filter on them. They do work on the routing side, which is another reason to drive DNS from the routing rule.
• logical or/and — sing-box DNS rules don't expose explicit and/or operators; matching is fixed (OR within a category, AND across categories).

If you try the routing-rule + DNS toggle flow and it doesn't cover your case, let me know what specifically you're trying to route and resolve — happy to look closer.

[jiegengxiangjianxue]

谢谢你的详细模板——抱歉你打字时手有点累！🙂

好消息：你问的大部分内容L×Box里已经有了，只是DNS设置界面里没有。它存在于路由规则编辑器（自定义路由规则→“+”）中，该编辑器有一个完整的可视化构造器，完全符合你列出的字段：

• 域名（精确）、域名后缀、域名关键词、IP CIDR——_匹配_部分
• 港口 / 港口范围——_港口_部分
• 应用包ID — _APPS_部分（应用选择器）
• 出站/路由行为 — 通道选择器

DNS页面没有单独构造函数的原因：在~90%的真实设置中，DNS规则应遵循其路由规则（相同的域名/应用→同一通道→由同一服务器解析）。所以，路由规则编辑器里没有让你重复构建规则，而是有一个DNS部分：

DNS→“Send DNS to dedicated server”→选择DNS服务器

开启后，规则会自动为你注册匹配的DNS规则——没有JSON，也没有重复条目。这就是你想要的可视化DNS编辑;只是通过路由规则而不是DNS界面访问。

因此，目前没有计划在 DNS 设置界面内建立独立的可视化构_造器——_建构器已经存在，DNS 会跟随路由规则运行。

由于歌唱盒的限制（不是我们的限制），在你的田野清单上有几个诚实的警告：

• 领域正则表达式——由单词框支持，但尚未以视觉形式呈现;目前它需要原始的JSON条目。
• 协议（http/dns/ntp/stun/tls/quic...）和网络（tcp/udp）——这些不会被针对基于Sing-box无头规则集构建的DNS规则进行评估，因此DNS规则无法对它们进行过滤。它们_确实在_路由端工作，这也是将DNS从路由规则中移除的原因之一。
• 逻辑 OR/AND ——Sing-box DNS 规则不暴露显式和/或操作符;匹配是固定的（类别内的匹配，以及类别间的匹配）。

如果你试过路由规则+DNS切换流程，但没能满足你的情况，告诉我你具体想路由和解决什么——我很乐意仔细看看。

I don't know how to put this into words, but you might want to check out Apple's paid proxy software: egern. It's really great, but unfortunately it only supports Apple devices. Next is karing - its traffic redirection feature is perfect for beginners. Lastly, there's husi, which supports more and newer protocols. Each software has its own strengths, but sadly none of them combine all the advantages of these other proxy apps. However, I think your software has a lot of potential, so I hope you can keep improving it. In the future, I'll keep submitting more feature requests to help you make lxbox even better

[Anilexis]

Can we select multiple DNS servers in case some of them are blocked/down?

[Cultsonfire]

Can we select multiple DNS servers in case some of them are blocked/down?

just enabling those dns servers should work, indicate as fallback if it doesn't work normally

[jiegengxiangjianxue]

Thanks for the detailed template — and sorry your hands got tired typing it! 🙂

Good news: most of what you're asking for already exists in L×Box, just not in the DNS Settings screen. It lives in the routing rule editor (Custom Routing Rules → "+"), which has a full visual constructor with exactly the fields you listed:

• Domain (exact), Domain suffix, Domain keyword, IP CIDR — the MATCH section
• Port / Port range — the PORT section
• App package ID — the APPS section (app picker)
• Outbound / routing behavior — channel picker

The reason there is no separate constructor on the DNS page: in ~90% of real setups a DNS rule should follow its routing rule (same domains/apps → same channel → resolved by the same server). So instead of making you build the rule twice, the routing rule editor has a DNS section:

DNS → "Send DNS to dedicated server" → pick a DNS server

Turning that on makes the rule automatically register the matching DNS rule for you — no JSON, no duplicate entry. That's the visual DNS editing you're after; it's just reached through the routing rule rather than the DNS screen.

A standalone visual constructor inside the DNS Settings screen is not currently planned for this reason — the constructor already exists and DNS rides along with the routing rule.

A couple of honest caveats on your field list, due to sing-box limitations (not ours):

• Domain regex — supported by sing-box but not yet surfaced in the visual form; for now it needs the raw JSON entry.
• Protocol (http/dns/ntp/stun/tls/quic…) and Network (tcp/udp) — these are not evaluated for DNS rules built from a headless rule-set in sing-box, so a DNS rule can't filter on them. They do work on the routing side, which is another reason to drive DNS from the routing rule.
• logical or/and — sing-box DNS rules don't expose explicit and/or operators; matching is fixed (OR within a category, AND across categories).

If you try the routing-rule + DNS toggle flow and it doesn't cover your case, let me know what specifically you're trying to route and resolve — happy to look closer.

The traffic redirection for LXbox is almost done now - we just need the most important logic: or, and, not. These three logical modes will greatly improve the efficiency of traffic redirection. Of course I have other ideas too, but right now the top priority is to implement these three logical modes so we can try out more traffic redirection features. Traffic redirection is really important for proxy software. Only a proxy that offers features that are easier for beginners to use and has a rich set of redirection options can be considered an excellent proxy software