A DNS failure may occur within a companys private network or within the Internet. The "Default Domain" An圜onnect Policy setting is not being used during the VPN session and increased DNS lookup latency (12 - 14 seconds between lookups), because the An圜onnect client is trying to use one search list and the workstation is being enforced by Group Policy to use another search list.Įven if we move the most common or most used DNS domain to the top of the Group Policy DNS Search List, there will probably still be a 12 - 14 second delay between the 1st and 2nd entry in the search list. The inability of a DNS server to convert a domain name to an IP address in a TCP/IP network. which may restrict the number of users that are allowed to access a site at any one time. HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\SearchList If an error message shows Service Unavailable DNS Failure. When an XP workstation's DNS Search List is managed by an Active Directory Group Policy, it uses the following registry key for the DNS Search list:
It appends the "Default Domain" An圜onnect Policy setting to the top of this registry key. HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\SearchList This option tells the Smoothwall to use its own DNS proxy service as the main. There are two global options: System internal DNS server User defined System internal DNS server. DNS settings are found in the 'Network - Configuration - DNS' menu. The An圜onnect client appears to modify and use the following registry key for the DNS Search List: DNS settings on a Smoothwall have multiple options used differently based on how its been deployed.