-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange DNS configuration thing #2327
Comments
u have in outbounds:
u should add to route.rules:
then u can remove this:
|
nope, that's not it, just tried this, and it still fails to resolve anything after removing that small snippet |
also I should mention, that removing absolutely every rule and setting final to proxy works, and no, this is not a solution or explanation to this problem, I still need rules |
You should put hijack-dns at the top right after direct rule for private ips. Your processes in the process rule can also send a DNS query and they will be routed to proxy outbound hence they will not get hijacked. "rules": [
{
"ip_is_private": true,
"outbound": "DIRECT"
},
{
"port": 53,
// "protocol": "dns", // available after sniff
"action": "hijack-dns"
},
{
"action": "sniff",
"timeout": "1s"
}
... |
oh well, your snippet works, although I still don't quite understand why my problem was happening, could you explain if you know what was happening? |
oh no, wait, it doesn't work, it doesn't route my traffic in my needed apps through proxy, here are my rules:
|
Oh well it works with domain rules, but it doesn't work with regex process paths with your snippet |
Operating system
Linux
System version
NixOS unstable, Linux 6.12.1
Installation type
Original sing-box Command Line
If you are using a graphical client, please provide the version of the client.
No response
Version
Description
I have this configuration
and if I remove this part
DNS stops working, like I can't resolve anything at all, and when I add this back, it works again, and I can't remove any part of this small snippet, if I remove that process_name part, it will also stop working, I can't find anything about this, why is this happening?
This was also happening on this configuration
Reproduction
yeet
Logs
No response
Supporter
Integrity requirements
The text was updated successfully, but these errors were encountered: