-
Notifications
You must be signed in to change notification settings - Fork 73
B2K - Routing Fails with DNS_PROBE_FINISHED_NXDOMAIN Error #650
Description
Describe the bug
I'm encountering an issue while using Bridge to Kubernetes for dynamic routing. After configuring everything, I consistently get the following error in the browser when trying to access the dynamically generated domain:
This site can’t be reached Check if there is a typo in defa-06e6.teo-sth.domain.local. DNS_PROBE_FINISHED_NXDOMAIN
Mention the platform you are using
VS 2022 v17.11.4
K8S v1.29.6
What I tried
I have configured the following Ingress resource in my Kubernetes cluster:

I also tested the Ingress configuration without a certificate to ensure TLS was not the issue, but the error persisted.
Host File Changes:
Added by Bridge To Kubernetes 127.1.1.2 mobile mobile.teo mobile.teo.svc mobile.teo.svc.cluster.local 127.1.1.1 teo-gw teo-gw.teo teo-gw.teo.svc teo-gw.teo.svc.cluster.local End of section
When starting the routing isolation, the process successfully modifies the hosts file on my local machine.
The base domain (teo-sth.paprec.com) resolves correctly. However, dynamic subdomains like defa-06e6.teo-sth.paprec.com fail to resolve, resulting in the NXDOMAIN error.
The logs of the routing-manager pod show no errors, and the ingress and isolated pods are successfully created.
Observations:
This seems to be purely a DNS resolution issue for dynamic subdomains.
I have confirmed that the ingress and pods are functioning correctly, as their configurations appear valid.
Expected behavior
Dynamic subdomains generated by Bridge to Kubernetes (e.g., defa-06e6.teo-sth.domain.local) should resolve automatically and route traffic to the appropriate isolated pod.
Screenshots
Here's a screenshot of all pods created, seems to be good

Logs:
Routing-manager logs
RoutingManager_logs.txt
Desktop (please complete the following information):
- OS: Windows 11
- Browser : chrome
- Version 131.0.6778.109
Blocking Issue
I’m completely blocked because the dynamic DNS resolution does not work, even though all other components (ingress, pods, routing manager) seem to function correctly.
If more details are needed, feel free to ask!
Thanks for reading !