cancel
Showing results for 
Search instead for 
Did you mean: 

Androind Pulse Secure DNS problem

kimmosummanen
Not applicable

Androind Pulse Secure DNS problem

Hi
Problem with Android Pulse Secure 6.0.1 when mobile device is in mobile data connection. vpn works but dns not. So we cannot access our internal resources with names, but using ip addresses resources opens nicely so vpn tunnel is working.

And if we connect to some public wifi network (and android gets some internal dns server addresses) then vpn works fine, we can access to internal resources with names when pulse vpn is connected. But if wifi gives to device public dns address then it is not working.

I did find some old post that seems quite same.
https://forums.pulsesecure.net/topic/pulse-connect-secure/173982-pule-on-android-split-tunneling-and-dns

Has anyone else run to this problem? Tested with Galaxy S7 with latest updates.
Tags (1)
7 REPLIES 7
zanyterp
Moderator

Re: Androind Pulse Secure DNS problem

That does not sound familiar.
What are your connection settings for DNS on the connection profile?
Are you using IPv6 or strictly IPv4? Does your cellular carrier use IPv6? Is there a proxy being used?
EduH64
Not applicable

Re: Androind Pulse Secure DNS problem

Same problem, Galaxy S5, v.6.0.1, DNS_PROBE_FINISHED_NXDOMAIN and others DNS errors. Connect but cannot access resources.
zanyterp
Moderator

Re: Androind Pulse Secure DNS problem

That sounds similar to an issue we have seen reported; however, I am not sure on the details
Can you please open a case with support for further investigation?
christine91
New Contributor

Re: Androind Pulse Secure DNS problem

Sometimes when you try to open the browser you get the error dns_probe_finished_nxdomain where the webpage is not available. This error occurs when DNS fails to translate. The easiest way to solve this problem on Google Chrome as well as all the other browsers is just follow the simple steps: 1. Alter the DNS IP Address 2. Flushing the DNS 3. Restarting the DNS Client 4. Resolving the 'dns_probe_finished_nxdomain' error in Android. Read the fulI solution here. I just found the solution here - http://errorcodespro.com/error-code-dns_probe_finished_nxdomain/
christine91
New Contributor

Re: Androind Pulse Secure DNS problem

Sometimes when you try to open the browser you get the error dns_probe_finished_nxdomain where the webpage is not available. This error occurs when DNS fails to translate. The easiest way to solve this problem on Google Chrome as well as all the other browsers is just follow the simple steps: 1. Alter the DNS IP Address 2. Flushing the DNS 3. Restarting the DNS Client 4. Resolving the [url=http://errorcodespro.com/error-code-dns_probe_finished_nxdomain/]dns_probe_finished_nxdomain[/url] error in Android.
Sofiane
New Contributor

Re: Androind Pulse Secure DNS problem

I can not connect from your Android phone j7 galaxe.
tomsrapper
New Member

Re: Androind Pulse Secure DNS problem

The reason for DNS_PROBE_FINISHED_NXDOMAIN is typically due to a misconfiguration or problem with your DNS. DNS is short for Domain Name System, which helps direct traffic on the internet by connecting domain names with actual web servers. Essentially, it takes a human-friendly request – a domain name like kinsta.com – and translates it into a computer-friendly server IP address – like 216.3.128.12.

When a user enters a URL in their web browser, DNS gets to work to connect that URL to the IP address of the actual server. This is called DNS name resolution and involves a DNS recursor querying various nameservers to figure out the actual IP address of a server. If DNS fails to resolve the domain name or address then you might receive the DNS_PROBE_FINISHED_NXDOMAIN error

There are simple steps that can lead to solving these problems. It is likely that you would not require any expert help because you can perform many of these techniques by yourself. The following are some of the steps you can adopt for solving the error DNS_PROBE_FINISHED_NXDOMAIN:

Alter the DNS IP address
Flushing the DNS
Restarting the DNS Client