Split DNS and wildcard issue - some are local some are remote
-
Without some exact ips, what is being used on your network, what your vpn settings are, I have no idea what is set to go through vpn and what not.
Maybe they only route their work networks through the vpn - that is very common practice.. And your local IP is stepping on your work network or tunnel network?
What does this machines routing table look like - simple route print from cmd line will show you that..
-
I talked with my IT and it's like you said: each time domain is needed it goes to company DNS and then if the IP is internal it goes through VPN and if not it doesn't. As for why my local domain behave like this...well...just because. And that's it. Simply it's how it works so unfortunately I still need NAT Reflection for my setup...
-
@Draghmar said in Split DNS and wildcard issue - some are local some are remote:
Simply it's how it works so unfortunately I still need NAT Reflection for my setup...
Split dns doesn't work if your not using your own dns.. To resolve the local -
Have to wonder why you would need to access your own local webserver while your "working" ;)
Just access it via IP if you do.. no dns involved. Or just create a host entry on the machine - so it knows fqdn points to local IP, and doesn't even need to ask work dns for it..
Other solution would be to run a conditional forwarder on your machine, say dnsmasq and not point your client to work dns, but the your conditional forwrder that only asks your work dns for work related domains.
Or depending on your work dns - you could setup pfsense to be the vpn client, and do policy routing with conditional forwarding for dns.
There are always many ways to skin the cat, in your case the simple solution would be yeah to use nat reflection. For this specific client.
