|
|
On Wednesday 03 March 2004 04:43 pm, John Locke wrote: > prepend domain-name-servers 192.168.9.39; > prepend domain-name "freelock.lan"; > > This puts my DNS server at the top of the list. Unfortunately this > means that when I'm not connected to the tunnel, name lookups take > FOREVER... (well, okay, maybe it's only a couple extra seconds). With > the tunnel, they're nice and speedy. > > I tried to append the domain name servers, but this didn't work > because my internal domain is obviously not recognized on the public > Internet. > > So... I'm still looking for a more elegant solution, that prepends > the name server only when the tunnel is up, and prevents it from > getting updated by renewing leases... but I have a workable solution. In your Openvpn config file you can specify a script to run when your vpn tunnel is finished connecting. Try having this script kill your dhcp client and restart it, but with the new config file - run dhclient with the old config at other times. Alternatively, you could run 2 dhclient processes - one on eth0 with the old config file, one on tun0 with the new config. Since the tun0 renews so much more often than eth0 you shouldn't run into conflicting data problems very often. Well, maybe... Dave ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |