Dns server slow to update

Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Start troubleshooting at the server that was used in your original query. Check whether this server forwards queries to another server by examining the Forwarders tab in the server properties in the DNS console.

If the Enable forwarders check box is selected, and one or more servers are listed, this server forwards queries. If this server does forward queries to another server, check for problems that affect the server to which this server forwards queries.

When that section instructs you to perform a task on the client, perform it on the server instead. If the server is healthy and can forward queries, repeat this step, and examine the server to which this server forwards queries. If this server does not forward queries to another server, test whether this server can query a root server. To do this, run the following command:. If the resolver returns the IP address of a root server, you probably have a broken delegation between the root server and the name or IP address that you're trying to resolve.

Follow the Test a broken delegation procedure to determine where you have a broken delegation. If the resolver returns a "Request to server timed out" response, check whether the root hints point to functioning root servers. To do this, use the To view the current root hints procedure.

If the root hints do point to functioning root servers, you might have a network problem, or the server might use an advanced firewall configuration that prevents the resolver from querying the server, as described in the Check DNS server problems section. It's also possible that the recursive time-out default is too short. Begin the tests in the following procedure by querying a valid root server.

The test takes you through a process of querying all the DNS servers from the root down to the server that you're testing for a broken delegation. Resource record type is the type of resource record that you were querying for in your original query, and FQDN is the FQDN for which you were querying terminated by a period.

If the response includes a list of "NS" and "A" resource records for delegated servers, repeat step 1 for each server and use the IP address from the "A" resource records as the server IP address. If the response does not contain an "NS" resource record, you have a broken delegation.

If the response contains "NS" resource records, but no "A" resource records, enter set recursion , and query individually for "A" resource records of servers that are listed in the "NS" records. Child Zones vs Zone Delegation. Skip to main content. Find threads, tags, and users Comment Show 0. I removed the entry and noticed the forwarded query timeout was equal to drumroll 5 seconds. Nothing really worked for me so hopefully this post will help others in the future. Update: A colleague of mine mentioned spyware interfering with proper DNS functionality resulting in intermittent resolution problems.

You can follow her on Twitter at cl. Available from dbatools. Available from dbachecks. After logging on to the server to troubleshoot, I could see that: Pinging external hostnames worked well after the hostname resolved.