![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 23%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFA%3C/text%3E%3C/svg%3E)
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
4,031 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 11%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJZ%3C/text%3E%3C/svg%3E)
Hello,
Thank you for posting in Q&A forum.
To further troubleshoot this issue, please kindly try below steps:
1.Go to the DNS server and make sure the forwarder configuration is correct.
2.Keep a network trace running in wireshark or network monitor on the DNS server, stop the traffice once this event logged. Search for "DNS" and IP address of forwarder to figure out if there's any DNS resolution failed.
3.Check the network condition on DNS forwarder and make sure it has proper connectivity to the address mentioned in log by ping command.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Best regards，
Jill Zhou
If the Answer is helpful, please click "Accept Answer" and upvote it.