mirror of
https://github.com/fosrl/newt.git
synced 2026-05-05 23:50:10 -05:00
[GH-ISSUE #222] When run in Podman newt tries to use the host's public IP as DNS #249
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JadedBlueEyes on GitHub (Jan 4, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/222
Describe the Bug
For some reason, newt tries to look up internal dns names using the host's public IP instead of Podman's DNS service. Hardcoding the IP works correctly. This is frustrating for dynamic IPs and ones set via the docker template.
Environment
To Reproduce
When set with the internal host as PANGOLIN_ENDPOINT:
external host starts correctly, but with internal host as target:
Expected Behavior
entering the container names should correctly look up the internal IP as it does in other containers
@oschwartz10612 commented on GitHub (Jan 20, 2026):
I think this is a podman issue! Newt just does a normal DNS lookup to the host. Closing for now...
@JadedBlueEyes commented on GitHub (Apr 4, 2026):
Hey, just coming back to this - it's likely that
cd4782265a/main.go (L308)defaults to 9.9.9.9 rather than the contents of resolv.conf - which includes the needed nameservers for things to work correctly.@LaurenceJJones commented on GitHub (Apr 6, 2026):
That
dnsoption is only for clients and wireguard tunnel not when resolving the Pangolin IP address that still uses the default resolver.