Bug: (root/nexttrace) DNS resolution fails on Termux because the package recipe does not apply the Android build fix

[tsosunchia]

Problem description

This issue is about the Termux package recipe for nexttrace, not a generic third-party software issue.

I am the owner of NextTrace(https://github.com/nxtrace/NTrace-core & https://github.com/nxtrace/NTrace-dev). We recently fixed Android DNS resolution issues on our side by adjusting the Android build configuration: enabling CGO for Android builds and using the Android NDK toolchain.

Reference:
nxtrace/NTrace-dev@ecec769

However, the current Termux recipe for nexttrace still appears to be built with the older generic Go build path. Since Termux builds nexttrace from source in termux-packages, the Android-specific upstream build fix also needs to be reflected in the package recipe here.

As a result, the nexttrace package distributed by Termux still shows DNS resolution failures on Android/Termux when resolving hostnames.

The current recipe I am referring to is:
https://github.com/termux/termux-packages/blob/master/root-packages/nexttrace/build.sh

What steps will reproduce the bug?

1. Install the package from Termux:
   pkg install root-repo
pkg install nexttrace
2. Run nexttrace example.com
3. Observe that hostname resolution fails on Termux.

What is the expected behavior?

nexttrace example.com should resolve the hostname normally on Termux.

The Termux package should be built with the same Android-specific fix that already resolves this DNS issue upstream, instead of continuing to use the old build configuration.

System information

None

[robertkirkman]

@tsosunchia you have TERMUX_VERSION=googleplay.2026.02.11, this indicates the presence of Google Play Termux and not F-Droid Termux.

• This page (termux/termux-packages) is the issues page for F-Droid Termux. If you meant to use Google Play Termux, please report this in the issues page for Google Play Termux here: https://github.com/termux-play-store/termux-issues/issues
• but if you meant to use F-Droid Termux, please try again using F-Droid Termux from here https://f-droid.org/en/packages/com.termux/

[tsosunchia]

@tsosunchia you have TERMUX_VERSION=googleplay.2026.02.11, this indicates the presence of Google Play Termux and not F-Droid Termux.

• This page (termux/termux-packages) is the issues page for F-Droid Termux. If you meant to use Google Play Termux, please report this in the issues page for Google Play Termux here: https://github.com/termux-play-store/termux-issues/issues
• but if you meant to use F-Droid Termux, please try again using F-Droid Termux from here https://f-droid.org/en/packages/com.termux/

Thanks for the clarification.

However, this issue is not about the app distribution channel itself (Google Play vs F-Droid), but about how nexttrace is being built for Android/Termux.

The upstream project has already fixed this DNS issue on Android by adjusting the Android build configuration (notably enabling CGO and using the Android NDK toolchain). If the Termux package is still built with the previous generic Go build path, the same DNS resolution problem will remain regardless of where the Termux app itself comes from.

So the key point of this report is that the nexttrace package recipe/build flags need to be updated to match the current upstream Android build requirements.

If needed, I can retest on F-Droid Termux as well and provide the result, but the root cause here should be the package build configuration rather than the Termux distribution channel.

[Biswa96]

I don't know what the expected nexttrace output should be but it seems to work in termux app from GitHub. The output of nexttrace contains my ISP's IP. So, I could not share it here.

[licy183]

Currently, Termux uses the NDK to compile all the goalng binaries, and CGO is always enabled. Termux has its own patch for the Golang resolver, but this patch only replaces the hardcoded /etc/resolv.conf with $PREFIX/etc/resolv.conf; the rest of the code paths remain unchanged.

I can't reproduce the failure either.

[robertkirkman]

If needed, I can retest on F-Droid Termux as well and provide the result, but the root cause here should be the package build configuration rather than the Termux distribution channel.

Please retest on F-Droid Termux as well and provide the result.