You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically, I'm curious if Envoy can support steps [3] and [5] in the diagram above:
Step 3: DNS resolver returns a synthetic IP (e.g., 100.80.10.10) for a hostname
Step 5: When traffic arrives at that synthetic IP's listener, Envoy can recover original hostname that was mapped
to this IP
I want to recover the original hostname because I want to upgrade traffic to HTTP CONNECT, which requires the original hostname in the CONNECT request.
The use case here is implementing wildcard egress policies (e.g., allow all *.aws.com traffic). With a wildcard policy, I don't know the fully qualified domain names until runtime (when the specific subdomains such as bucket1.aws.com is resolved). I'd prefer not to use SNI so that I can support all kinds of traffic.
Would Envoy be able to:
Track DNS resolution mappings (hostname → synthetic IP)
Retrieve the original hostname when traffic arrives at the synthetic IP
Make this hostname available to the tunneling configuration
Is this a feasible addition to Envoy? Or is there an existing mechanism I'm missing that could achieve this? Thanks in advance ~
In our setup we would use dns_filter for dns resolution, and the aim is to preserve the host and resolved ip mapping and for that mapping to be available in the tcp proxy filter.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
@ovadiagal@AntonKanug I don't think it's supported natively today but it should be possible to write a custom module in GoLang/RUST and load it up via Dynamic Modules. You could make it to an inline lookup, populate a cache for faster subsequent lookup and flush the {hostname, resolved IP} info in Dynamic Metadata or Filter State. You can write another module to map it back to the hostname.
It might also be possible to share the context between two Dynamic Modules.
cc @mathetake
This prototypes provides the needed functionality for our usecase. Given that this is a niche usecase we can cherrypick this change and maintain it in our envoy fork, happy to also get this merged if it adds value to public envoy.
@agrawroh are you/envoy team is open to merging these filters/changes? given these change gives you the features from the cloudflare article linked above all in envoy this seems like something other envoy users could benefit from.
@AntonKanug Is it not possible to use Dynamic Modules as I suggested? You could write a GoLang or RUST extension for your use-case. If you do want to contribute and add it then you could do so here in this fork.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Activity
[-]Wildcard hostname resolution[/-][+]Retrieve DNS resolution results at runtime[/+]AntonKanug commentedon Oct 17, 2025
In our setup we would use dns_filter for dns resolution, and the aim is to preserve the host and resolved ip mapping and for that mapping to be available in the tcp proxy filter.
RyanTheOptimist commentedon Oct 27, 2025
cc: @yanavlasov @mattklein123
AntonKanug commentedon Nov 19, 2025
@yanavlasov @mattklein123 bumping ^, any thoughts on this?
github-actions commentedon Dec 20, 2025
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
agrawroh commentedon Dec 20, 2025
@ovadiagal @AntonKanug I don't think it's supported natively today but it should be possible to write a custom module in GoLang/RUST and load it up via Dynamic Modules. You could make it to an inline lookup, populate a cache for faster subsequent lookup and flush the
{hostname, resolved IP}info in Dynamic Metadata or Filter State. You can write another module to map it back to the hostname.It might also be possible to share the context between two Dynamic Modules.
cc @mathetake
AntonKanug commentedon Dec 20, 2025
@agrawroh We have given this a shot by writing 2 filters, one in the dns filter to do wildcard dns resolution and store it in a cache, and one to look that cache up from. https://github.com/envoyproxy/envoy/pull/42631/changes
This prototypes provides the needed functionality for our usecase. Given that this is a niche usecase we can cherrypick this change and maintain it in our envoy fork, happy to also get this merged if it adds value to public envoy.
AntonKanug commentedon Jan 9, 2026
@agrawroh are you/envoy team is open to merging these filters/changes? given these change gives you the features from the cloudflare article linked above all in envoy this seems like something other envoy users could benefit from.
agrawroh commentedon Jan 20, 2026
@AntonKanug Is it not possible to use Dynamic Modules as I suggested? You could write a GoLang or RUST extension for your use-case. If you do want to contribute and add it then you could do so here in this fork.
github-actions commentedon Feb 19, 2026
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
AntonKanug commentedon Feb 19, 2026
For completeness, @ovadiagal is working on this feature via dynamic modules envoyproxy/dynamic-modules-examples#56 and has a working version
Add `dns_gateway` dynamic module example (#56)
github-actions commentedon Mar 21, 2026
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
github-actions commentedon Mar 28, 2026
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.