You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Pierre-Luc Dion (JIRA)" <ji...@apache.org> on 2016/04/13 02:59:27 UTC

[jira] [Updated] (CLOUDSTACK-8874) Nslookup is failing from the remote access vpn client

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Luc Dion updated CLOUDSTACK-8874:
----------------------------------------
    Fix Version/s:     (was: 4.6.1)
                   4.6.2

> Nslookup is failing from the remote access vpn client
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-8874
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8874
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Devices
>    Affects Versions: 4.3.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.6.2
>
>
> Steps to reproduce:
> 1. Enable VPN for a guest network.
> 2. connect to the VPN using any supported VPN client, make sure the DNS is provided by the VPN(default).
> 3. After connecting check the name server in use by 'NSlookup'.
> 4. Try resolving any hostname, either an instance name or any other.
> 5. It should fail.
> 6. Login to the VR.
> 7. run 'netstat -anp | grep 53' output should only have dnsmasq listening on guest interface.
> 8. modify /etc/dnsmasq.conf' and add 'interface=ppp0' , as per the output of ifconfig ppp0 is the name, or pppX.
> 9. Restart the dnsmasq service and the netstat output now contains the VPN tunnel interface IP for port 53.
> 10. Name resolution works from VPN client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)