Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Performance Impact and Risks of Switching from On Demand to Persistent DNS

Performance Impact and Risks of Switching from On Demand to Persistent DNS

Table of contents
Created by Mindy.Kerber, last modified by MindTouch on Jun 23, 2016

Views: 786 Votes: 0 Revisions: 3


When you setup Orion NTA to run NetFlow collections through the NetFlow Service with the On Demand DNS option, the software writes IP addresses into the Orion database where they are referenced in the event that an Orion NTA module needs addresses resolved in order to display its relevant statistics.

Currently, if you switch from On Demand to Persistent DNS, the Orion NTA software does not seek DNS answers for any IP that already exists in the Orion database. Any new IP address is automatically resolved, however.


Orion NTA 3.6 and 3.7


There is no permanent resolution of this issue and the workaround has an important caveat. The workaround is to to run a database script (below) against the Orion database each time you switch the Orion NTA software from the On Demand to the Persistent DNS configuration. The result of the script is that the NetFlow Service immediately begins to resolve every IP address currently listed in relevant table of the Orion database.

This DNS work is resource intensive in the short run, and can seriously impact the performance of your overall Orion network management implementation, since it resolves the usually large existing list of IP addresses in the database. Also, after the big job of resolving the existing IP addresses is finished, the NetFlow Service may permanently command intensive resources to keep up with the DNS work involved in routinely processing incoming flow data.

Assuming your system is up to the task, to prepare for the switch from On Demand to Persistent DNS configuration in Orion NTA, run the following database script:

SET @RC = 1

WHILE (@RC > 0)
            INSERT INTO NetFlowAddressToResolve
            SELECT TOP 50000 e.IPAddressSort, 1, GETDATE()
            FROM NetFlowEndpoints e
                                    LEFT JOIN FlowCorrelationPostDNS p ON e.IPAddressSort = p.IPAddressSort
                                    LEFT JOIN NetFlowAddressToResolve r ON e.IPAddressSort = r.IPAddress
            WHERE p.IPAddressSort IS NULL AND r.IPAddress IS NULL

            SELECT @RC = @@ROWCOUNT




Last modified