-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add compatibility for Android #13
Comments
Please test again. |
|
Please try again |
This was performed without any filtering between the android device, and router (which is using NextDNS DoT).
And again, over mobile connection with NextDNS DoH filtering via AdGuard for Android.
|
Are you running nextdns or another form of local dns proxy? Please try again without if any. |
AdGuard was not running as a local DNS proxy, it was running as a local VPN. To clarify, there is no changes to the default Mobile network settings other than setting native Android DNS to the NextDNS endpoint (DoT).
|
An without DoT or any other non basic DNS settings? Seems like go think your resolver is localhost but nothing answers in port 53. Could be a behavior triggered by dns encryption or dns software or vpn. |
Absolutely everything has been turned off, the device is now running on a raw mobile connection.
|
This may very well have something to do with it. https://stackoverflow.com/questions/38959067/dns-lookup-issue-when-running-my-go-app-in-termux |
Yes it is, but then there is no automated way to run this diag, as forcing 8.8.8.8 will give a false picture as it is probably not the name server used by the OS. |
It seems that your recent change introducing mktemp call in run.sh caused a regression on Edge routers: This tool will download a small binary to capture latency and routing information The source code of this tool is available at https://github.com/nextdns/diag Do you want to continue? (press enter to accept) On Edgerouter OS mktemp argument must have following form: |
Thanks for the heads up, please check again. |
It works now, thanks. |
Could Android compatibility be added for this tool?
For the sake of curiosity, I ran this under an Android 11 environment via Termux and was given the following output:
The text was updated successfully, but these errors were encountered: