re: dns route ralayed by vpn concentrator not reachable

Unanswered Question
May 29th, 2007
User Badges:

i am working on a setup wherein we have configured remote access vpn for our customers using a vpn concentrator 30xx series herein we are able to establish the ipsec tunnel and reach all the subnets on the inside of the concentrator however the dns route relayed or pushed from the concentrator to the client is not reachable ,we have a pix firewall behind the concentrator which has been configured to allow all the traffic coming in from the ipsec endpoints , when i check the routes on the endpoint device that is the vpn client machine i have a dns route with the tunnel gateway as the next hop except this specific route i have a default route on the client as well , the catch herein is that when i remove the specific dns route i am able to reach the dns server which was earlier unreachable , i am able to reach the dns server by means of the default route which has the same next hop as the specific route mentioned earlier.just need to clarify whether i have missed any configuration on the concentrator.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
amritpatek Tue, 06/05/2007 - 05:20
User Badges:
  • Silver, 250 points or more

There could be no specific reason for this as source and destination address in IP is going to remain the same in either case.Is the DNS request traffic from the client reaching the concentrator when specific route is mentioned. If not for the specific route set the next hop as Interface if ip address was mentioned before else set the ip address as next hop if interface was mentioned before.

Actions

This Discussion