Yes, that is the wall I am hitting in that I need to be able to enter
http://hostname in a browser because unfortunately our sharepoint intranet was never configured to respond to fqdn. I configured the default dns suffix but it doesn't seem to be working either. When the only default route present while connected to the vpn is the vpn tunnel gateway it works, obviously, but when my local def route is present also and the ovpn route is superseding it, traffic does route through the tunnel like it is supposed to but
http://hosdtname doesn't work.
With our current Juniper vpn, once connected the local default route is actually replaced with the Juniper route while connected and upon disconnecting the route goes back to normal. With ovpn the reason it feels like it isn't truly routing ALL traffic over the tunnel is because
http://hostname won't resolve whereas if it was sending that over the tunnel it would. We really want to make this solution work because it is cheaper and we need about 500 seats. Plus it is easier to manage than the Juniper but this will be a show stopper.
Is there perhaps a way to push a host override to clients to force my
http://hostname to an IP? If i set an entry in my windows host file it works but pushing this via group policy doesn't solve for users trying to use vpn from their home computers.
