In news:237587EB-FB7B-4409-99EC-08CD5188277A@microsoft.com,
Quo Vadis <quovadis@news.postalias>, posted the following:
I assume you are saying that the client's mydomain.org name is not their own
public record, or does it belong to them?
Either way, I can suggest in such a 'same name internal as external name'
scenario, to create a hostname called "virtual" under the zone on the
internal DNS server, and provide your own WAN IP. This way once connected to
the VPN, the VPN connection assumes to use the internal DNS server IP
addresses for queries, so when you connect to virtual.domain.org, it will
use the internal DNS server to resolve it. This is because a client machine
will use the VPN adapter settings first, over it's own DNS settings. Now if
your VPN doesn't use the internal DNS, it may not be configured properly to
use it.
If you are connecting from externally *prior* to establising the VPN, then a
hosts record, as Danny suggested, is the only way to work.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.