You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At our company, we access shared environments via VPN (Cisco AnyConnect Client). The client then mangles the system's DNS resolver stack so that "internal" hostnames can be resolved properly while the user is connected to the VPN.
This method works for all std CMD line tools, such as ping, etc.
Nelson, however doesn't seem to be picking up the newly changed DNS stack.
Temporary fix: manually edit your /etc/hosts to add the needed hostname(s)
The text was updated successfully, but these errors were encountered:
At our company, we access shared environments via VPN (Cisco AnyConnect Client). The client then mangles the system's DNS resolver stack so that "internal" hostnames can be resolved properly while the user is connected to the VPN.
This method works for all std CMD line tools, such as ping, etc.
Nelson, however doesn't seem to be picking up the newly changed DNS stack.
Temporary fix: manually edit your /etc/hosts to add the needed hostname(s)
The text was updated successfully, but these errors were encountered: