Sophos Community
Site
User
Site
Search
User
All Groups
Intercept X Endpoint
XG Firewall
UTM Firewall
Sophos Partners
Community Chat
Support Portal
Feedback on Product Documentation
Community Blogs & Events
Community Calendar
Sophos Community Blog
Community Security Blog
Getting Started
Member Recognition
Community Leaderboards
Sophos Partner Recognition
Sophos Techvids
Product Documentation
Support Portal
Sophos.com
More
Cancel
Advisory: Support Portal Maintenance. Login is currently unavailable,
more info available here.
UTM Firewall
VPN: Site to Site and Remote Access
Different DNS servers for split-tunneling L2TP
Release Notes & News
Recommended Reads
Forums
UTM Top Contributors 2020
Early Access Programs
More
Cancel
New
Thread Info
State
Not Answered
Locked
Locked
Replies
3 replies
Subscribers
0 subscribers
Views
4486 views
Users
0 members are here
Options
RSS
More
Cancel
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Different DNS servers for split-tunneling L2TP
MatthiasFleschuetz
over 15 years ago
I've set up a L2TP split-tunnel vpn with WinXP to Astaro 6.100.
IP is working very fine, but DNS makes problems.
I get the DNS server by the astaro when connecting the vpn, the dedicated DNS suffix is configured also.
Although everything seems to be configured fine, all applications (browser, email, etc.) seem to take the primary DNS server and not the VPN-DNS-server when requesting a hostname with the DNS-suffix registrered to the L2TP tunnel.
Does anybody know how to configure WinXP properly to work with different DNS server, corresponding to the DNS-suffix?
Thanks a lot,
Matthias
This thread was automatically locked due to age.
0
BarryG
over 15 years ago
Not elegant, but you could:
1. set DNS servers statically (turn of DNS via DHCP)
2. put the VPN DNS server's IP as the first DNS server in Windows, and the local as second.
That way, when you're connected to the VPN, it'll use that one, otherwise it'll time out and use the internal.
The timeouts may be a problem though... you'll have to try it.
Barry
Cancel
Up
0
Down
Cancel
0
MatthiasFleschuetz
over 15 years ago
in reply to
BarryG
[ QUOTE ]
Not elegant, but you could:
1. set DNS servers statically (turn of DNS via DHCP)
2. put the VPN DNS server's IP as the first DNS server in Windows, and the local as second.
That way, when you're connected to the VPN, it'll use that one, otherwise it'll time out and use the internal.
The timeouts may be a problem though... you'll have to try it.
[/ QUOTE ]
Hi Barry,
thanks for the answer, but unfortunately I cant use such a setup for several reasons.
1. I am not always connected via VPN so the vpn-dns-server is not always reachable.
2. The VPN-DNS-server is just an internal server, so it does not know the internet records...
What I want is a connection based setup, so everything with domain.local should work over l2tp (including dns resolving for this domain), everything else should go through the normal ethernet line.
Thanks,
Matthias
Cancel
Up
0
Down
Cancel
0
JaZZ
over 15 years ago
Hello,
i hope that helps.
http://support.microsoft.com/kb/311218/en-us
Cancel
Up
0
Down
Cancel