Re: 2 DNS servers, one for Internet, one for AD
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Jun 2007 15:44:43 -0400
Jo Stick <jo@xxxxxxxxx> wrote:
Thanks for responding. My own PC is behind a firewall, as is the
office, so there is no security problem there. The VPN is between the
firewalls. I guess I wasn't clear with my question. What I woul dlik
eto achieve is for my PC to do its name resolution for non-work
domain addresses through the ISP DNS server, but to still register
with the office DNS and use it for LAN lookups. All works if I only
have the office DNS in my PC settings, but internt is slower to
browse as it involvees going to office server though VPN rather than
straight up to ISP.
Jo
Well....you probably aren't going through the office network to get to the
Internet - just for your DNS resolution. Unfortunately, there's no way to
make this work as you wish. Your computer's communication with AD will be
very badly screwed up if you use anything other than the office DNS server.
If there's a terminal services box, or WinXP Pro box, in the office network,
it won't matter what you have in your own IP config; you can initiate an RD
session to the office, and then use your own browser (locally) to surf,
using your ISP's DNS servers. And performance for pretty much everything
will be a lot better, because very little will actually be going across the
slow VPN link (just screen shots).
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:ePQfUuBuHHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Jo Stick <jo@xxxxxxxxx> wrote:
I work remotely, connected by VPN to the office server and Active
Directory. For AD to wotk properly, I need to use the office server
for DNS, but this makes Internet lookups slow. Is there a way to
have my remote PC direct Internet DNS queries to my ISP but still
retain the use of the office DNS where appropriate?
thanks for help,
Jo
You'd need to disable the "use remote gateway" option in your VPN
client (if this is permitted) but note that this is a bad idea from
a security perspective. You'd be exposing your company's network to
any traffic coming in to your own. And yes, having anything other
than the internal DNS server in can cause AD problems.
If your office has a terminal server, or an XP Pro box you can use
for Remote Desktop, that might be a better option.
You really ought to talk to your office IT folk about this, I think.
.
- References:
- 2 DNS servers, one for Internet, one for AD
- From: Jo Stick
- Re: 2 DNS servers, one for Internet, one for AD
- From: Lanwench [MVP - Exchange]
- Re: 2 DNS servers, one for Internet, one for AD
- From: Jo Stick
- 2 DNS servers, one for Internet, one for AD
- Prev by Date: Re: best dns config for new tree in forest
- Next by Date: W2003 DNS Event 4515
- Previous by thread: Re: 2 DNS servers, one for Internet, one for AD
- Next by thread: Re: 2 DNS servers, one for Internet, one for AD
- Index(es):
Relevant Pages
|
