Hey the above code attempt to resolve the rewrite address either using the ip/cidr notation or by performing a DNS lookup. If parsing fails or dns fails we still relay the packet to the VIP?
Im looking at adding an internal DNS cache since every new connection will perform a dns lookup which adds latency to every request (until a net state is created) which we can perform the lookup for a user, then cache for a TTL.
However, it seems that forwarding even if resolution fails is not correct behavior, asking in case it was intentional?
Originally created by @LaurenceJJones on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/206
https://github.com/fosrl/newt/blob/d5e0771094f8f729b4dda80b6048dd4098f4fec5/netstack2/proxy.go#L463-L471
Hey the above code attempt to resolve the rewrite address either using the ip/cidr notation or by performing a DNS lookup. If parsing fails or dns fails we still relay the packet to the VIP?
Im looking at adding an internal DNS cache since every new connection will perform a dns lookup which adds latency to every request (until a net state is created) which we can perform the lookup for a user, then cache for a TTL.
However, it seems that forwarding even if resolution fails is not correct behavior, asking in case it was intentional?
@github-actions[bot] commented on GitHub (Jan 20, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
<!-- gh-comment-id:3770622246 -->
@github-actions[bot] commented on GitHub (Jan 20, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 4, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
<!-- gh-comment-id:3844587503 -->
@github-actions[bot] commented on GitHub (Feb 4, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @LaurenceJJones on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/fosrl/newt/issues/206
https://github.com/fosrl/newt/blob/d5e0771094f8f729b4dda80b6048dd4098f4fec5/netstack2/proxy.go#L463-L471
Hey the above code attempt to resolve the rewrite address either using the ip/cidr notation or by performing a DNS lookup. If parsing fails or dns fails we still relay the packet to the VIP?
Im looking at adding an internal DNS cache since every new connection will perform a dns lookup which adds latency to every request (until a net state is created) which we can perform the lookup for a user, then cache for a TTL.
However, it seems that forwarding even if resolution fails is not correct behavior, asking in case it was intentional?
@github-actions[bot] commented on GitHub (Jan 20, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 4, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.