Workflow - DNS Tests
Hello,
I am building workflows that test critical network connectivity. One of the tests I want to perform is to check multiple DNS servers by making a basic query to each one. The DNS lookup function doesn't appear support this kind of advanced testing.While some advanced DNS lookup options would be a nice feature, I'd prefer to just be able to execute a windows command and have the results added to the workflow results. In this case, I'd want to do "nslookup <cr> server 1.2.3.4 <cr> something.important.com <cr> server 1.2.3.5 <cr> something.important.com <cr> " for example.
Having the ability to run windows commands and have their results dumped into the workflow output without having to put them in any type of script would be a huge plus. I think it'd be better to add this ability before working on refining the existing tools, such as the DNS lookup function, since several short comings that might exist could be easily addressed with some basic DOS troubleshooting commands. This would give users the ability to do whatever they need to do without having to wait for the feature to be added at a later date/time. Just a thought...
I am building workflows that test critical network connectivity. One of the tests I want to perform is to check multiple DNS servers by making a basic query to each one. The DNS lookup function doesn't appear support this kind of advanced testing.While some advanced DNS lookup options would be a nice feature, I'd prefer to just be able to execute a windows command and have the results added to the workflow results. In this case, I'd want to do "nslookup <cr> server 1.2.3.4 <cr> something.important.com <cr> server 1.2.3.5 <cr> something.important.com <cr> " for example.
Having the ability to run windows commands and have their results dumped into the workflow output without having to put them in any type of script would be a huge plus. I think it'd be better to add this ability before working on refining the existing tools, such as the DNS lookup function, since several short comings that might exist could be easily addressed with some basic DOS troubleshooting commands. This would give users the ability to do whatever they need to do without having to wait for the feature to be added at a later date/time. Just a thought...