- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
11-01-2019 08:31 AM
Hi Team
1. After connected the global protect DNS resolution is not happening. but i can able to do ping 8.8.8.8.
2. In nslookup google.com also resolved. But if I ping the same google.com dns is not resolving.
3. If I browse any website, that is not working due to dns resolution issue.
My dns IP is 8.8.8.8. Is anyone experienced like this type of issue. Please suggest some resolution for this
Best regards
Mohammed Asik
11-01-2019 09:26 AM
In traffic logs, I could see the session reason end was " aged out". But everything seems to be expected.
For internet traffic NAT applied and could see destination address ip has been resolved. but in web browser its not resolved ( tried the same thing with three different machines.
ingress interface --> tunnel.2 and egress interface --> eth 1/2 as per the configuration
11-01-2019 09:30 AM
for DNS and web-browsing traffic bytes sent/received increment equally (or more less)?
11-01-2019 01:56 PM
@MohammedAsik Do you have DNS Suffix configured in Agent configuration ??
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!