Forum Discussion
External private IP addresses registering with DNS server
We are experiencing the exact same issue, please respond if you found a resolution to this issue.
Hohmaniacs1 Ditto! I'm seeing their home LAN IP as well as their VPN IP. This is totally strange. I'm assuming it has something to do with our Firewall because when I connect in via Azure VPN instead of our default Firewall VPN no DNS record even shows up for my test device.... now I have 2 concerns. Unable to reach an Azure connected client and having an unroutable LAN IP address in my DNS. Weird.
I have a case open with Microsoft, will update when I hear anything. So far they have no clue.
Think I may have found the cause of our VPN Endpoints forwarding their VPN IP as well as their home LAN IP in our internal DNS. There was a IP Helper set in our Fortigate Firewall that was set to "help" DNS pass though. After disabling it then connecting to VPN from my test machine I'm now only seeing the routable VPN IP address and not the Endpoints Home LAN IP address. I tried removing the invalid DNS entries but they slowly show back up, it appears this setting may require an endpoint to disconnect and then reconnect in order to be applied.
Dunno if that will help your situation but that appears to be what was causing our DNS issue.
Correction: This did not resolve our DNS issue for remote clients. I'm leaving that up as an idea for others but I did finally find out what is causing it. If a user connects from home and is hardwaired and connected via WiFi, they then connect to VPN and the tunnel utlizes one adapter. The adapter it isn't using is the IP address of the device that gets added to our DNS. The Local LAN IP address of the adapter VPN is utilizing is NOT added to our DNS.
I've still yet to find a solution to this other then disabling the WiFi adapters or disabling the "Register this connection's address in DNS".
