I have recently done some external DNS changes via Network Solutions. I am
having problems when people connect to the VPN. They cannot connect to
local resources via FQDN. When I do a nslookup on the working computers the
first server fails with something like:
request timed out on 65.108.234.55(arbitrary)
Then it defaults to my internal DNS server. I am afraid that the computers
are not taking the default DNS servers as they should. VPN clients are
supposed to use the DNS of the remote(internal) domain, correct? I have
read around and found that
http://support.microsoft.com/default...b;en-us;311218 will fix the
issue. But I find it awefully coincidental that this problem just started
to occur when I did some changes to DNS at Network Solutions. But this
doesn't make sense because VPN clients are supposed to be using the
remote(internal) DNS. I am lost. Anyone want to with this mess?

-Steven-

In news:uYrBzAoUGHA.4156@TK2MSFTNGP10.phx.gbl,
Steven Platt <me@nowhere.com> typed:
> I have recently done some external DNS changes via Network Solutions.
> I am having problems when people connect to the VPN. They cannot
> connect to local resources via FQDN. When I do a nslookup on the
> working computers the first server fails with something like:
> request timed out on 65.108.234.55(arbitrary)
> Then it defaults to my internal DNS server. I am afraid that the
> computers are not taking the default DNS servers as they should. VPN
> clients are supposed to use the DNS of the remote(internal) domain,
> correct? I have read around and found that
> http://support.microsoft.com/default...b;en-us;311218 will
> fix the issue. But I find it awefully coincidental that this problem
> just started to occur when I did some changes to DNS at Network
> Solutions. But this doesn't make sense because VPN clients are
> supposed to be using the remote(internal) DNS. I am lost. Anyone
> want to with this mess?

What kind of changes did you make?
It has been a while since I made changes with NetSol's DNS servers, but did
you happen to enable the Wildcard record in the public domain? ( I believe
the record is something like "all other names" and only requires placing a
check in a box)

Wildcard records can cause real headaches for the MS DNS client service and
nslookup that appends the domain name to all queries not ending with a
trailing ".". This will cause any query to resolve to the Wildcard record.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================