I have one server that I have a problem with this one component on the DNS app monitor. The DNS User Experience monitor shows down on this one server. I have the monitor configured with default settings. I am able to ping solarwinds.com from the server in question and it resolves to the IP 74.115.13.20. The monitor works on other servers in the same domain with the same DNS setup. I have checked everything I could on the server regarding DNS and all looks good. There are no actual issues occurring on the server regarding DNS. All other DNS components in the monitor show up.
The error I receive when doing a test on this component against this server is:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
I enabled debug logging on this monitor and let it poll. I'm going to paste in here what I think is the relevant part of the debug log for this issue. Any ideas would be helpful. I think the issue is related to the actual monitor not being able to communicate properly to test this particular component. But it's testing all the other components in the same monitor without issue.
2015-03-11 15:44:25,114 [STP Pool:263 Thread #0] [C30618] DEBUG SolarWinds.APM.Probes.ProbeExecutors.RegularBatchExecutor - Component probe starting: JobContext - NodeId: 6325, NodeName: servername.somewhere.com, ApplicationId: 1936, ApplicationName: Windows DNS Server, ComponentId: 30618, ComponentName: DNS User Experience Monitor, CustomLogEnabled: True
2015-03-11 15:44:25,114 [STP Pool:263 Thread #0] [C30618] DEBUG SolarWinds.APM.Probes.DnsQAProbe - Start DNS lookup.
2015-03-11 15:44:25,114 [STP Pool:263 Thread #0] [C30618] DEBUG SolarWinds.APM.Probes.DnsQAProbe - Name to resolve 'solarwinds.com' detected as domain name
2015-03-11 15:44:25,114 [STP Pool:263 Thread #0] [C30618] DEBUG SolarWinds.APM.Probes.DnsQAProbe - Target's IP address is '172.23.6.99'
2015-03-11 15:44:25,114 [STP Pool:263 Thread #0] [C30618] DEBUG SolarWinds.APM.Probes.DnsQAProbe - Begin lookup of 'solarwinds.com' on '172.23.6.99' DNS server
2015-03-11 15:44:27,361 [STP Pool:263 Thread #1] [C0] DEBUG SolarWinds.APM.Probes.PerformanceCounters.ManagedCounterFetcher - Creating counter DNS_Database Node Memory__172.23.6.99
2015-03-11 15:44:27,938 [STP Pool:263 Thread #1] [C0] DEBUG SolarWinds.APM.Probes.PerformanceCounters.ManagedCounterFetcher - Creating counter DNS_Nbstat Memory__172.23.6.99
2015-03-11 15:44:28,500 [STP Pool:263 Thread #1] [C0] DEBUG SolarWinds.APM.Probes.PerformanceCounters.ManagedCounterFetcher - Creating counter DNS_Record Flow Memory__172.23.6.99
2015-03-11 15:44:29,077 [STP Pool:263 Thread #1] [C0] DEBUG SolarWinds.APM.Probes.PerformanceCounters.ManagedCounterFetcher - Creating counter DNS_Dynamic Update NoOperation/sec__172.23.6.99
2015-03-11 15:44:29,639 [STP Pool:263 Thread #1] [C0] DEBUG SolarWinds.APM.Probes.PerformanceCounters.ManagedCounterFetcher - Creating counter DNS_Dynamic Update Received__172.23.6.99
2015-03-11 15:44:29,701 [STP Pool:263 Thread #0] [C30618] ERROR SolarWinds.APM.Probes.DnsQAProbe - SocketException caught. SocketError: TimedOut
System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at SolarWinds.Net.Dns.Resolver.UdpTransfer(IPEndPoint server, Byte[] requestMessage)
at SolarWinds.Net.Dns.Resolver.Lookup(Request request, IPAddress dnsServer, Int32 dnsPort, TransferType transferType)
at SolarWinds.APM.Probes.DnsQAProbe.QueryDNS(String nameToResolve, Node dnsServer, Int32 portNumber, TransferType transferType, Boolean expectAll, String expectedAnswerlist, PortMonitorNumericResult result)
at SolarWinds.APM.Probes.DnsQAProbe.ProbeInternal(ProbeInformation configuration, PortMonitorNumericResult result)
2015-03-11 15:44:29,701 [STP Pool:263 Thread #0] [C30618] DEBUG SolarWinds.APM.Probes.DnsQAProbe - Outcome - Fail.