[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 779
  • Last Modified:

cant resolve DNS over site-to-site VPN

I have a Linksys WRVS4400N Wireless Router w/ VPN configured to VPN into our main offices PIX. The VPN is up, and working, I can connect to anything from our remote office to our main office, so long as I use the IP.

remote office is 192.168.x.x
main office is 192.168.y.y

if I point my laptop's DNS to our main office DNS server, I can query places like google.com, and yahoo.com, no problem. I cannot however query srv01.domain.biz, assuming domain.local as my main offices internal domain.

did a nslookup with "set norecurse" and it spits back our external DNS servers as ns records, rather than the server we queried, which is authoritative for domain.biz

Any ideas on why our remote office isn't getting proper responses?
0
mnswhit
Asked:
mnswhit
1 Solution
 
George LauIT ManagerCommented:

 Let's assume you have your numbers correctly set, and your internal NS records are in order at your business. Perhaps the laptop is holding on to the residual NS numbers?

Start-->Run
cmd [click ok]
ipconfig /flushdns [enter]
(You should see a message about successfully flushing the DNS resolver cache.)
ipconfig /registerdns [enter]
(...another message about DNS registration.)

Try pinging srv01.domain.biz...


This is the easy solution. The next could possibly be your VPN concentrator is overriding DNS to the client...let's not go there unless we need to. :) I'd need to know a little more about the far end.

Good luck,
T

0
 
e3userCommented:
hey there

I dont know if did this but in the group-policy you should put the ip of the DNS servers:

group-policy vpnpolicy attributes
     dns value 78.xxx.xxx.xxx  79.xxx.xxx.xxx

if it is possible to show run and display it here
0
 
mnswhitAuthor Commented:
I did try the ipconfig /flushdns and all. I ended up calling Cisco and Linksys in a conference call. After monitoring traffic on the PIX, we discovered that DNS was not going through the VPN. Running a sniffer on the laptop, it appears that the Linksys WRVS4400N was responding to the DNS queries even though it was not the DNS that was queried. Linksys now has a bug report on the issue.

Their suggestion was to utilize LMHOSTS file, which we are now doing. Thank you for your responses though.
0

Featured Post

Choose an Exciting Career in Cybersecurity

Help prevent cyber-threats and provide solutions to safeguard our global digital economy. Earn your MS in Cybersecurity. WGU’s MSCSIA degree program was designed in collaboration with national intelligence organizations and IT industry leaders.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now