eh? what the ... I expected the tests, results and formatted output of the old tool. My shock in being presented with this dumbed down and fluffy replacement is almost as great as my disappointment that something i valued is now unlikely to be renewed.
I hope whatever changes you do make you do the following at the very least - restore the table layout, maintain the order of the tests of the previous tool, contain at least all the old tests of the old tool, restore the technical detail and get rid of the new fluff.
Sorry to be so negative, but DNSReport was a magic tool, thorough, quick and easy to parse the results. I can hardly focus on the page of this new version.
Thanks! The specifics are very helpful. We'll be doing a ton of side-by-side comparisons of the old and new tools, so these are good things to keep our eye on.
The new format of the DNS Stuff Domain Reports I confess I have tried to come to like but don't. It looks nicer but it's actually harder to use, at least for us and our clients.
We would often print the old format report before going in to a prospective client pitch meeting. The lack of color was great because the yellow and red color blotches let everyone focus right away on the problem areas and the technical detail was right there too. With the new report format we actually have to read each section to figure out whether there is a problem or not -- and then we take a yellow highlighter to the printed copy to mark which areas need attention.
We often made use of the "email link" generator to circulate a report to various folks who needed to see it. It was easy for us and the recipient to use, and gave DNS Stuff a nice plug to the recipient. Everyone feels now like you are in the email harvesting business, so instead we print the report to a pdf and email the pdf instead. More work and less plug for DNS Stuff.
I like that the report itself appears more modern, but it's functional efficiency has gone way down unfortunately.
Hope that helps,
This information about exactly what you're using the data for and how is really helpful - that helps us walk back through your steps and test any design concepts to make sure we're providing that functionality.
Hopefully we can strike a balance between the value, visibility, detail, and organization of the previous report and improved usability based on what we know now that you're all coming to DNSreport for (issues and the detail behind them, results of ALL tests - even those that passed - with the details behind them, etc).
In total agreement with all comments so far. Have been a paid user for 3 years and I don't think I'll be renewing this year. Tools used to be much faster and more accurate. Quite frustrating now after many years of great service. Most frustrating is the amount of times I wait for the tools to deliver no results after an IP search or reverse lookup.
Hope you folks are able to rectify the situation or at least revert back to a functional version of the site.
Most frustrating is the amount of times I wait for the tools to deliver no results after an IP search or reverse lookup.
I wanted to make a note specifically on this: we had an issue over the last 24-48 hours where the tools performance degraded to the point where many pages were NOT returning results. This was resolved yesterday/today and we're hoping to avoid it in the future. We're also introducing more traceability into the tools, so that when they do fail customers can report a transaction ID that lets us identify exactly what happened and improve the site.
We're also taking a hard look at performance between the two sites (old vs. new) from the point you submit the search to all results being presented; we'll use those results to track down lingering issues. Right now, there does seem to be a performance issue with traceroute specifically that we've narrowed down, but we'll be looking through all of the tools.
Hey DNSreport Feedback Crew,
Thanks to our UX team, I've got a mock-up of a version that tries to focus on the issues addressed in this thread where it applies.
Some things you won't see in the mockup but we will address separately, including:
Notes on the attachment:
Without further adieu, here's the sample (click for full size if it's too small):
So, what do you think of the new-old formatting?
This is just pixels, it's relatively easy for us to tweak at this stage. We'd like to get it right.
The mockup png is much better for our needs on first glance, thank you!
When we are speaking with C-level execs, they need to be able to gravitate quickly toward the issues, and have something they can then hand to their internal IT folks with enough technical detail for the IT folks to be able to resolve the issue quickly.
Can you also restore the report link generator we could then cut 'n paste into emails? Asking others to register gets in the way of their seeing the reports quickly, and with all due respect comes across as email harvesting...
Thanks, Mark. I will take a look at what the old DNSreport did for the e-mail linking - I imagine there was an authentication bypass if you were accessing it from an e-mailed link and we overlooked that with the move (there was a similar case with Mail Server Test Center where a couple of tools needed to bypass the normal authentication mechanisms, so it looks like we found one more).
OK, a great step in the right direction. I like the ability to save it as a PDF and email.
One thing I noticed on the current is mistake in the way the response is being read. In the MX section on the SMTP Greeting, It is reporting a failure when in fact the failure is on the part of how the report is looking at the data. In the picture I included, the very first part of the line is 250-smtp38.gate.dfw1a.rsapps.net which is correct data and should be labled as a Pass.
I am not sure about having the entire line colored rather than just the status column.
Also, the originator of DNSTools prefers email over e-mail. I have the email to prove it.
Any way of seeing a full report to give feedback on section by section?
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.