However if you're seeing this message very often (for example every 60 seconds) it could indicate a clash with other software on your computer. It's normal to see this message every now and then (for example when a DHCP renew occurs). If this is a problem you should consider removing the DNS Domain from the listed network interface.ĭNS change detected, restoring DNS settings: This message indicates that the DNS settings were changed by a process other than Viscosity, and Viscosity is restoring the DNS settings back to your VPN DNS settings. This could potentially cause DNS lookups to travel via a different network interface when using Split DNS. DNS resolution attempts for this domain may not use the VPN DNS server/s or fail to resolve.: This warning indicates that a VPN DNS domain is already in use on the computer. WARNING: The DNS domain is already in use by interface.
Please refer to the information in the Reserved Domains section for information about this warning.
Using it as a standard DNS domain may cause DNS lookups to fail and break Split DNS setups. local domain is a special domain reserved for use by mDNS. Using it as a DNS domain may cause DNS resolution attempts to fail or unexpected DNS behaviour.: The. local domain is present in the DNS domain list. Please refer to the article about this warning which covers how this warning can be resolved. The DNS server/s for this connection may not be used.: This indicates that the connection needs one or more DNS domains to be specified, or the DNS mode changed, for DNS to work correctly. WARNING: Split DNS is being used however no DNS domains are present. In some rare instances this may be intentional and the warning can be ignored. This warning typically indicates either incorrect DNS server/s have been specified, or a problem with the VPN connection's routing. DNS lookups will not take place over the VPN connection. This could result in DNS lookups failing, or unexpected DNS results.
: This warning indicates that the IP address of the DNS server isn't being routed through the VPN connection. DNS lookups to this server may travel over a different network interface. WARNING: The DNS server is not routed through the VPN connection. If any problems are found, it will add a warning to the OpenVPN log with more information. Viscosity will automatically check for potential configuration problems with a VPN connection's DNS setup. If you have established you have a DNS issue, you should first check the OpenVPN log for any relevant messages. If you're sure you have a DNS problem after performing these steps, then please proceed to the troubleshooting sections below. Please refer to the "Unable To Use The VPN Connection" section in the Troubleshooting Connection Problems article and follow the steps to test your VPN connection. Often other configuration problems and routing problems can cause DNS lookups to fail, however ultimately it isn't the DNS configuration that is at fault. It's important to first establish you have a problem with your VPN connection's DNS setup before continuing. However before continuing please make sure you have followed instructions in the Troubleshooting Connection Problems article to establish the cause of any issues using your VPN connection. This article aims to walk you through solving common configuration mistakes and issues that can cause DNS lookups to fail for a VPN connection.
0 kommentar(er)
