Re: VPN Client Name Resolution

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

anonymous_at_discussions.microsoft.com
Date: 05/19/04 

Date: Wed, 19 May 2004 10:15:58 -0700

Yes, the vpn/ras clients get a dhcp assigned ip address,
dns address, etc. It appears, however, that this may not
be the "preferred" route for resolving these names.

We have two zones in our AD integrated DNS; one is for
the "internal only" domain and one is for the
second "company.org" domain that has addresses that
resolve on the Internet.

Jason

>-----Original Message-----
> When the remote clients connect, they should receive
the DNS server
>address as part of the connection process. This should be
the DNS address
>configured on the RRAS server, which should be your
internal DNS server. So
>the remote clients should be using the same DNS server as
the LAN clients
>when they are connected to the intranet by VPN. Do you
have the remote
>clients configured to obtain the name server
automatically in their
>connection properties?
>
>"Jason E" <help@youth-guidance.org> wrote in message
>news:eacb01c43d10$2fc3f900$a401280a@phx.gbl...
>> We have an Intranet we would like to make available over
>> the Internet.
>> We want to be able to design the Intranet site so it
uses
>> names resolvable internally by our dns to LAN ips, and
>> extrernally to public IPs. Eg. data.company.com when
>> connected to the LAN resolves to a 192.168.1.x and the
>> same name resolves to 67.153.212.x when accesses from
the
>> Intrernet.
>> This setup works fine until my VPN clients come into the
>> mix. They try to resolve the name to the external
>> address, but I need them to resolve it to the internal
>> address in order to access the resources through the vpn
>> tunnel.
>> The VPN tunnels terminate at a RRAS server, not a multi-
>> homed VPN server. The whole shebang is behind a 3rd
party
>> firewall.
>>
>> Suggestions?
>> Thanks!
>> Jason E
>
>
>.
>

Relevant Pages

  • Re: DNS dfs issue
    ... You say that some clients are OK. ... The domain controllers for SiteA are named: ... No matter which dns server I use on clientB1 its %logonserver% is always ...
    (microsoft.public.windows.server.dns)
  • Re: NS and domain A record affecting AD
    ... Clients are pointing to the local dc for both WINS and DNS, ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS server resolved 64.106.154.50 to all domain name
    ... I am doubting that this will resolve things. ... the DNS server but in the DNS caching resolver client. ... >> Usually if you deselect "Append parent suffixes of the primary DNS ...
    (microsoft.public.windows.server.dns)
  • Re: newbie lost in trying to setup NAT
    ... That is what you have DHCP for. ... You set the clients to obtain an IP ... address automatically and to obtain their DNS server automatically. ...
    (microsoft.public.windows.server.networking)
  • Re: Creating my first user accounts
    ... I am trying to log onto the domain with the clients to have access to shared ... files and access the internet. ... DNS is almost always the cause of authentication errors -- ... Did you alter the DNS server settings, ...
    (microsoft.public.windows.server.active_directory)