- Would you mind showing where you have seen broken links so we can get this corrected? Also, what were you trying to paste that it wouldn't allow? Our platform should handle almost anything you feed it.
- I've tested replying to the DNSstuff Welcome post with several registered user accounts and did not receive an error. Could you try replying to that post again and providing us a screenshot of the error page?
I've sent your comments over to the Product Manager, look out for her response to follow.
To address the site-specific questions:
I have been patiantly waiting to see how things are progressing before making any comments, but now the time has come.
3) The changes to DNSreport are horrible. I have seen mention that customers were surveyed and input recieved, but no one ever asked me.
You definitely aren't the only person that is having trouble with the DNSreport changes. The best place for any specific feedback on DNSreport you'd like to add is in this thread: DNS Report Feedback & Thoughts. We're collecting all the feedback we can about the tool and changing the UI based on all of that feedback. Customers were surveyed on other DNSstuff UI feedback, but not specifically on the changes to DNSreport, so we're taking a step back, soaking up your comments, reviewing the old and new sites, and looking for a solution.
4) I have reported a problem wiht running a DNSreport on the company I work for. Somehow, DNSstuff is injecting a phantom MX record that is scewing the results horribly. SolarWinds has acknowledged this problem but todate the problem has not been resolved and it is still there.
This is a bug for sure and several people have reported it. If you have opened a support case, you will be notified as soon as we've verified your specific issue is resolved on the production live site. Some DNSreport issues in this area (unexpected MX records showing up) have been fixed while a few others remain open. We'll keep rolling site updates out as we have confirmed fixes, and if they are significant I'll update the blog post with comments: What's Up with DNSstuff: Professional Toolset, Infrastructure, and What's Next.
5) Trying to run a spam database report takes 3-4 times before getting a result. Before it shoes error messages.
I'm guessing this is the "We're sorry, but we were unable to execute your request" error? We're seeing this intermittently with some customers, and some people never see it at all. We're still investigating. We've mostly seen it with DNS report and DNS lookup, but those are also by far the two most popular tools, so it's possible it's just more common by virtue of more visibility.
Do you see this with any other tools, or just the "Spam Database Lookup" tool (or is it another)? Is it better/worse with different domains or from different computers/locations?
Thanks for all of the feedback! One of the posts in the DNS report feedback discussion thread (mentioned above) includes a little flavor on how long the changes have been in the making, if you're curious about where it started.