feedback/

[giscus[bot]]

feedback/

Dear MintFlow NetStack users, We are willing to hear your feedback.
Please comment in this page for bugs and feature requests.
Also you can create issue on Github for submit issues for the app: Submit GitHub Issue

Also you can join our community on Telgram: Join Our Group

Also you can write msg to mintflow@galaxnet.cc
to get support.

https://galaxnet.cc/mintflow/feedback/

[ToFu2244]

Hi there! Thank you so much for creating this app. It's exactly what I was looking for!
I have one request: Would it be possible to support wildcards for domain sets? Currently, I have to add every entry manually, one by one. Having *.example.com would make things easier. Thank you!

[mintflow]

Hi, thanks for feedback, do you mean that you want to match all subdomains of example by using *.example.com?

If you mean that, the domain list in the domain set is used to match all the domains have the suffix, that is equal to *.example.com from what I can see.

The reason we do this is to reduce configuration typing overhead.

[ToFu2244]

I also thought that's how it would work, but this is not the case. My DNS server uses split DNS internally within my network, and the same address resolves externally with a different IP address. However, despite split DNS being enabled in Mintflow, it resolved the public IP address instead of the internal one. This was then routed through the WireGuard tunnel with the external IP address, which didn't work. Only after adding my.example.com to the domain set did the internal IP address resolve correctly.

Setup:

my.example.com
  internal: 192.168.0.100
  external: 1.2.3.4

CIDR set: Home
  - 192.168.0.0/24

Domain set: Home
  - example.com

Both sets are routed through WireGuard. When I try to open my.example.com, the DNS logs show the IP address 1.2.3.4 and indicate that it is being routed through the WireGuard tunnel because the domain set still matches. However, the site cannot be reached internally using the external IP address.

If I specify the site in addition to the root domain, however, it works as intended: the IP address resolves to 192.168.0.100 via the split DNS settings in Mintflow, and the domain set is used for routing.

Domain Set: Home
  - example.com
  - my.example.com

[mintflow]

Hi,

Since you said you have enabled the split DNS (which I think you mean the home screen's App Routing toggle enabled).

In that case, the routes action of the Domain Set Home decide which DNS server it use, as I can see from your description, it get routed to the Wireguard interface, so it should use the VPN DNS servers configured in the split dns of the settings screen.

If the above is true, the DNS should be resolved by your VPN DNS server, may I know what DNS server you use for the VPN DNS server?

Also you said that you have checked the DNS logs under the tool screen, do you notice for the log, what's the action of the domain log shown for the two diffrent domains? This will show us what DNS server it will use to resolve the domain.

[woodj4101]

Excellent app! I hope Split DNS with DoT and DoH will be supported in the future. DoQ and DoH3 might be a bit too much to ask for, but it would be great if they were supported someday!

[mintflow]

Hi there,

Thanks for your suggestion, we are currently add profile and scritping engine support into the app.

For the DoT/DoH support, since our internal DNS server do support the features though we do not expose it to the end user, we will evalute them and consider add it in the future versions.

Stay tuned.

[woodj4101]

I would like to request a feature that allows all DNS queries to be routed through a specific VPN, regardless routing type, while App Routing is enabled.

I am running AdGuard Home on my homelab, and for security reasons, only WireGuard is exposed to the internet. My mobile device is always connected to my homelab via WireGuard, and I would like to ensure that all DNS traffic from the device is consistently routed through WireGuard and resolved by AdGuard Home.

[mintflow]

Hi there,

This is a really reasonable requirement, in current version when we program iOS network settings, we exclude the direct dns servers to go into our network engine to make direct query directly sent over the local internet.

The coming version of mintflow app will focused on dns related enhancement, such as DoT/DotH support, this feature will also be added by introduced a switch (such as direct-dns-server-no-exclude=true to enable it).

Thanks a lot for this great feedback.

[unixapple]

Hi there , this feature is supported in the latest version

So I close this issue

Feel free to submit new frs