By default, nslookup sends queries to DNS servers on UDP port 53. If the server is located on another network that is reachable only through an intermediate host (such as a packet filtering router or proxy server), the DNS server might use a non-standard port to listen for and receive client requests. In rare cases, the DNS server might have an advanced security or firewall configuration. You can try a different IP address in the list or add the IP address to the list. If the DNS server has been configured to limit service to a specific list of its configured IP addresses, it's possible that the IP address that's used to contact the DNS server is not in the list. On the Interfaces tab of the server properties page in the DNS console, administrators can restrict a DNS server to listen on only selected addresses. If the issue occurs when the service is running, the server might not be listening on the IP address that you used in your nslookup query. Try to restart the DNS Server service by entering the following at a command prompt on the server: net start DNS ![]() If the resolver returns a "Request to server timed out" or "No response from server" response, the DNS service probably is not running. You can learn whether it's paused by checking the General tab of the zone properties in the DNS console. If the resolver returns a "Server failure" or "Query refused" response, the zone is probably paused, or the server is possibly overloaded. If the resolver returns the IP address of the client, the server does not have any problems. Run the following command and check whether the DNS server is reachable from client computers. Or, in an administrative PowerShell window, run the following cmdlet: Clear-DnsServerCacheĬheck the following logs to see whether there are any recorded errors: To do this, run the following command in an administrative Command Prompt window: dnscmd /clearcache If you get a failure or time-out response, see Checking for recursion problems.įlush the resolver cache. If so, see Checking for problems with authoritative data. Run ipconfig /all at a command prompt, and verify the IP address, subnet mask, and default gateway.Ĭheck whether the DNS server is authoritative for the name that is being looked up. ![]() This article discusses how to troubleshoot issues on DNS servers. Message="VM has reported a failure when processing extension 'vmssCSE'.Try our Virtual Agent - It can help you quickly identify and fix common DNS issues. It's likely custom DNS server is not correctly configured, please see for more information.ĭetails: Code="VMExtensionProvisioningError" When you try to create an AKS cluster, you receive the following error message:Īgents are unable to resolve Kubernetes API server name. ![]() If Azure CLI is already installed, you can find the version number by running az -version. The nslookup DNS lookup tool for Windows nodes or the dig tool for Linux nodes.Īzure CLI, version 2.0.59 or a later version. This article discusses how to identify and resolve the K8SAPIServerDNSLookupFailVMExtensionError error (also known as error code ERR_K8S_API_SERVER_DNS_LOOKUP_FAIL, error number 52) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
0 Comments
Leave a Reply. |