Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAT/DNS issue in internal network - how does a car resolve and cache DNS records? #297

Closed
slashrsm opened this issue Jan 8, 2025 · 1 comment
Labels

Comments

@slashrsm
Copy link

slashrsm commented Jan 8, 2025

I have a fleet telemetry stack running on a server in my local network. I have to use NAT to forward requests from the internet to the server.

When the car is away from home everything works great. When I return home and car connects to my WiFi it is unable to connect to the fleet telemetry server.

DNS records for the telemetry servers differ depending on where you are. When away they will resolve to the public IP of my router and when at home they will resolve to the internal IP of the server.

Based on the error messages that I get from the car it seems that it fails to connect because it never got the internal DNS record. It is still trying to connect to the public IP address, which at that point is my router and not the fleet telemetry server.

My questions are:

  1. How long will the car cache DNS records? Will it try to re-fetch them when connected to a WiFi?
  2. Will car use the DNS server that the DCHP server propagates or it always uses its own?

Anyone else experienced the same problem? How did you resolve it?

@patrickdemers6
Copy link
Collaborator

Specific behavior of the vehicle regarding DNS isn't available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants