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
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:
How long will the car cache DNS records? Will it try to re-fetch them when connected to a WiFi?
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?
The text was updated successfully, but these errors were encountered:
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:
Anyone else experienced the same problem? How did you resolve it?
The text was updated successfully, but these errors were encountered: