Web 2.0 really changed everything. I'm not talking about the technology behind Web 2.0 companies, but the whole aspect of user generated content.
Here I was writing a review of Branding for Dummies. A few hours laters one of the authors (Barbara Findlay Schenck) leaves a comment on my blog. Pretty cool, hum?
In an Web 1.0 style you'd go to Amazon.com and leave your review and rating of the book there. Sure this author would probably read it, but the solution is not a forum for a conversation. Not only that, but when I write posts on my blog, I control the content. I can review it, delete it or link to other posts or sites that might interest me. Traditional Web 1.0? Nope, you can't do that.
This is not a rant about Amazon or any of the traditional Web 1.0 sites. This is a post to show the power of Web 2.0 for consumers and users, like you and me.
I also want to ackowledge that any smart business person is listen carefully to what their consumers / clients / users are doing, and Barbara did just that. She probably has a Google Alert, or Technorati Feed on her name or her book title, like I do, so, when anyone writes anything about her, she will be the first to know and ready to react.
Hope that someone reading this blog can help me with this problem (or know someone who can). And the story goes like this...
Three users have recently reported being unable to access their Sampa site. They can access pretty much any site on the Internet but not a Sampa site (e.g. http://marcelo.sampasite.com)
Data points:
Sampa sites (*.sampasite.com) use our own DNS system (on ns1.sampasite.com, 207.115.80.185)
NSLOOKUP for these users return the correct IP address: 207.115.80.185
Internet Explorer, on the other hand, cannot reach the site giving a DNS-like error (e.g. “This page cannot be displayed”)
They can access www.sampa.com (207.115.80.184) which is on the same network, but uses Windows DNS
Sampa sites don’t have reverse DNS (don’t think this matter)
The problem is that NSLOOKUP works fine, but IE cannot resolve the address (one user tried using Firefox and it didn’t work either). I don’t know if NSLOOKUP uses Microsoft’s DNS Client, or it has its own Socket implementation. I don’t even know where to start this investigation short of asking people to install a network sniffing tool, which is probably way beyond these users’ ability.
I want to write some C++ debugging tool that I can give to these users to help them identify the problem, but I’m not sure where to start.
Anyone has any idea of what else I can investigate to get to the bottom of this issue? Could this be some anti-phishing tool problem?
Subscribe to this Site
(207.115.80.184) which is on the same network, but uses Windows DNS
January, 2008