Question : Problem: Local domain name same as FQDN - VPN clients name resolution problems

I have a client with small network consisting of few 2000/2003 servers.
The Local Domain name inherited from old NT network was named "domain.ca", as it happens there is a valid FQDN called "domain.ca".

Da Problem:
VPN clients have problems with name resolution of the internal servers and devices.

I do not want to setup HOSTS files on Noteboks used by VPN clients, as I would have to change them every time I have a change on the network.
Useras are using standard windows PPTP VPN client.

Wonder if somone have figured out some other way to deal with something like that.

I have tried adding "internal" DNS and WINS in the VPN client settings with no luck - the client picks up the resolution from the web.

Answer : Problem: Local domain name same as FQDN - VPN clients name resolution problems

Internal DNS should work, but my guess is you are seeing the problem in:

     http://support.microsoft.com/kb/311218

You can go here:

     http://www.isascripts.org/

Download the zip file and you can use the script ISA_DNS_Binding_Order.vbs on the vpn clients.