For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

schmuck's avatar
schmuck
Icon for Nimbostratus rankNimbostratus
Apr 30, 2014

Inbox VPN and DNS

We are currently testing the Inbox VPN functionality. We are currently unable to resolve hosts using the DNS entries that we create in the Network Access settings. If we attempt to ping Intranet, the name does not resolve and therefore does not ping. If we attempt to ping Intranet.domain.com, the name does not resolve and therefore does not ping. If we try and ping Intranet via it's IP address, it replies fine telling us the tunnel is working properly. Also, if we attempt to ping -a ipaddress it will resolve to Intranet and ping properly. We have tested against multiple F5 clusters with the same results. We have also tried to create an on-domand tunnel with no luck, http://support.f5.com/kb/en-us/products/big-ip_apm/releasenotes/related/config-note-f5-inbox-vpn-client-windows8.html. Any thoughts?

 

availability
BIG-IP Access Policy Manager (APM)
deployment
security

3 Replies

  • kunjan's avatar
    kunjan
    Icon for Nimbostratus rankNimbostratus
    Jun 06, 2014

    You can use 'netsh namespace show policy' to check NRPT(Name Resolution Policy Table) that is used to resolve DNS in Inbox VPN. If google there are cases of corrupted NRPT and bugs. May be you are hitting one of those.

     

  • schmuck's avatar
    schmuck
    Icon for Nimbostratus rankNimbostratus
    Jun 11, 2014

    Thanks for the reply. When I run the above command I just get an empty table. Is anyone else trying to get this working or better yet, have it working? If so, does the above command return data or is it empty as well???