{"action":"created","issue":{"url":"https://api.github.com/repos/Tunnelblick/Tunnelblick/issues/305","repository_url":"https://api.github.com/repos/Tunnelblick/Tunnelblick","labels_url":"https://api.github.com/repos/Tunnelblick/Tunnelblick/issues/305/labels{/name}","comments_url":"https://api.github.com/repos/Tunnelblick/Tunnelblick/issues/305/comments","events_url":"https://api.github.com/repos/Tunnelblick/Tunnelblick/issues/305/events","html_url":"https://github.com/Tunnelblick/Tunnelblick/issues/305","id":155756259,"number":305,"title":"DNS for split-tunnel configuration overwrites previous resolvers","user":{"login":"xortim","id":901298,"avatar_url":"https://avatars0.githubusercontent.com/u/901298?v=3","gravatar_id":"","url":"https://api.github.com/users/xortim","html_url":"https://github.com/xortim","followers_url":"https://api.github.com/users/xortim/followers","following_url":"https://api.github.com/users/xortim/following{/other_user}","gists_url":"https://api.github.com/users/xortim/gists{/gist_id}","starred_url":"https://api.github.com/users/xortim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xortim/subscriptions","organizations_url":"https://api.github.com/users/xortim/orgs","repos_url":"https://api.github.com/users/xortim/repos","events_url":"https://api.github.com/users/xortim/events{/privacy}","received_events_url":"https://api.github.com/users/xortim/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2016-05-19T14:50:46Z","updated_at":"2017-04-20T11:08:03Z","closed_at":null,"body":"Firstly, thanks for the awesome project!\n\nThis is more of a behavioral question/issue. Serving DNS, assigned via DHCP is a common practice. The tunnelblick up/down scripts handle assigning the DNS servers to the host machine, however it appears that resolvers that were previously defined are no longer used after connecting to the VPN.\n\nIs it possible to append the DNS resolvers to the hosts' existing resolvers?\n\nThe scenario in which this is needed:\n- Corporate network employs split-DNS. Ex: mail.company.com internally resolves to 192.x.x.x, and externally it resolves to 68.x.x.x.\n- OpenVPN has been set up on a hosted network such as EC2 or RackSpace to provide access into this environment.\n  - DNS is configured inside of this environment.\n  - DHCP sets the name server.\n  - Split Tunnel is enabled to allow users to access the internal resources of the company such as git.company.com.\n\nWhen connected, the DNS settings which resolves internal addresses for the internal resources are no longer resolving, instead they are resolving to their public addresses if available.\n\nWithout disabling split tunnel, is it possible to use another DHCP option that Tunnelblick will honor to append the VPNs resolvers (which don't forward requests for other zones).\n\nIdeal state is that if the nameservers prior to connecting to the VPN are:\n- 192.168.1.1\n- 192.168.2.1\n\nAnd the DNS resolvers set by the VPN are:\n- 172.16.1.1\n- 172.16.1.2\n\nThen the VPN client would have the following resolvers:\n- 192.168.1.1\n- 192.168.1.2\n- 172.16.1.1\n- 172.16.1.2\n\nIs this possible using TunnelBlick as the client?\n"},"comment":{"url":"https://api.github.com/repos/Tunnelblick/Tunnelblick/issues/comments/295686532","html_url":"https://github.com/Tunnelblick/Tunnelblick/issues/305#issuecomment-295686532","issue_url":"https://api.github.com/repos/Tunnelblick/Tunnelblick/issues/305","id":295686532,"user":{"login":"MarSik","id":171090,"avatar_url":"https://avatars1.githubusercontent.com/u/171090?v=3","gravatar_id":"","url":"https://api.github.com/users/MarSik","html_url":"https://github.com/MarSik","followers_url":"https://api.github.com/users/MarSik/followers","following_url":"https://api.github.com/users/MarSik/following{/other_user}","gists_url":"https://api.github.com/users/MarSik/gists{/gist_id}","starred_url":"https://api.github.com/users/MarSik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MarSik/subscriptions","organizations_url":"https://api.github.com/users/MarSik/orgs","repos_url":"https://api.github.com/users/MarSik/repos","events_url":"https://api.github.com/users/MarSik/events{/privacy}","received_events_url":"https://api.github.com/users/MarSik/received_events","type":"User","site_admin":false},"created_at":"2017-04-20T11:08:03Z","updated_at":"2017-04-20T11:08:03Z","body":"The common use case for our company is a home office scenario. Local home connection is used for everything except company private addresses. This means we need to rely on two DNS systems - the ISP one for the public internet and the VPN provided one for internal network.\r\n\r\nOur company IT currently recommends (paid) Viscosity over Tunnelblick because of this issue."}}
{"actor":{"display_login":"MarSik"}}