Is there anyway of troubleshooting dns resolution? As it stands it appears to be speratic. Here is the license information: Module Name User Device TrackerVersion2.0.0Service PackNoneLicenseProductionAllowed number of monitored ports25000Current number of monitored ports17961 I have only implemented this in the last couple of days, so its very new.

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

dns resolution

Is there anyway of troubleshooting dns resolution? As it stands it appears to be speratic.

Here is the license information:

Module Name	User Device Tracker
Version	2.0.0
Service Pack	None
License	Production
Allowed number of monitored ports	25000
Current number of monitored ports	17961

I have only implemented this in the last couple of days, so its very new.

Find more posts tagged with

Accepted answers

All comments

plagerism

It appears that only 1026 ips have been resolved of over 4110.

plagerism

After some further investigation I found a whole heap of the following segfaults in the UDT.BusinessLayer log. The exact cause is unknown and it doesnt happen to every node every time and some more often than others.

2012-07-17 09:39:21,373 [ 63] ERROR - Error while processing job 'N:499|DNS' (da71a0f4-f64c-4f1b-b10b-aab84e818a91) [SolarWinds.UDT.BusinessLayer.Polling.UDTDnsResultProcessor]

System.IndexOutOfRangeException: Index was outside the bounds of the array.

at SolarWinds.UDT.BusinessLayer.ExtensionMethods.ToIPHostEntry(UDTDnsJobResult result)

at SolarWinds.UDT.BusinessLayer.Polling.UDTDnsResultProcessor.<DoProcessing>b__d(UDTDnsJobResult entry)

at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()

at System.Linq.Buffer`1..ctor(IEnumerable`1 source)

at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)

at SolarWinds.UDT.BusinessLayer.Polling.UDTDnsResultProcessor.DoProcessing(UDTJobResult jobResult)

at SolarWinds.UDT.BusinessLayer.Polling.UDTJobResultProcessorBase.Process(UDTJobResult jobResult)

I have a ticket open for this now, I was just wondering if anyone has experienced similar issues.

Bedrich.Michalek

This exception can cause some hostnames are lost. It's fixed in the upcoming UDT 2.5.

plagerism

So this is a known issue? From what I can see it doesnt cause just "some hostnames to be lost" it appears that all hostnames related to the Layer3 Poller. Whens 2.5 going to be available? Is there a release schedule for it? I am new to the solarwinds product.

cvachovecj

Hi,

There is currently UDT 2.5 beta available. You can subscribe here: SolarWinds UDT 2.5 Beta Participation Survey

If you have maintenance agreement and want to, we can include you in customer acceptance phase -- please let me know if you want to know more details.

Regards,

Jiri

bluefunelemental

I can confirm for my install that 2.5 resolved the lack of DNS hostnames showing - minutes after the update to 2.5 I saw all of them even before the next poll.

Sneaky 2.0 was just hiding them from us the whole time.