Question about nameserver-policy wildcard support: Is "*" a valid catch-all?

[arash1959]

Hi developers,

I have a question regarding the nameserver-policy configuration in Mihomo.

In the official Wiki, it is mentioned that "Keys support domain wildcards," and examples like "+.google.com" or ".google.com" are common. However, I would like to clarify the behavior of a single asterisk "" as a key.

1. Is "*" officially supported as a "catch-all" or "fallback" rule within nameserver-policy to match all domains not specified in previous rules?

2. Is there any technical difference between using "*" and "+" (plus sign) for this purpose?

3. Some users report that "*" works in practice but isn't explicitly documented as a standalone wildcard. Could you clarify if this is a reliable behavior or if it's better to use default-nameserver-policy instead?
   My Configuration:

nameserver-policy:
"geosite:ir": [178.22.122.100, 185.51.200.2]
"*": ["https://1.1.1.1/dns-query", "https://8.8.8.8/dns-query"]

Thank you for your hard work on this amazing core!

[gdarmstadtiumberkelium]

emm, no!

You might not have read the full documentation:
https://wiki.metacubex.one/en/handbook/syntax/#domain-wildcards

1. * only matches hostnames without a dot (.), such as localhost.
2. There is no option using only + for this purpose. The closest is +.*, which represents a match-all rule.
3. default-nameserver is used for resolving the domain names of DNS servers. I think what you actually need is simply the nameserver https://wiki.metacubex.one/en/config/dns/diagram/

nameserver-policy:
  "geosite:ir": [178.22.122.100, 185.51.200.2]
nameserver: ["https://1.1.1.1/dns-query", "https://8.8.8.8/dns-query"]

Additionally, the official core is maintained at:
https://github.com/MetaCubeX/mihomo
while OpenClash is a LuCI plugin (though it does add features like the "smart" policy group).