The ISPs Who Route Around VeriSign
from the good-for-them dept
Broadband Report is naming some of the ISPs who are routing around VeriSign's attempt at hijacking all typo traffic with their SiteFinder service. Interestingly, a bunch of them are pointing people to Google instead. I don't necessarily see why Google deserves that traffic either. Why not just put it back to normal and give me back my "page not found" information?
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Reader Comments
Subscribe: RSS
View by: Time | Thread
huh 'page not found'?
How is 'page not found' correct?
Is it not *MORE* correct to say 'cannot resolve host'? Or how about: whatever.blah.name.com could not be found. Please check the name and try again.
Why ask for more broken behavior of 'page not found'?
[ link to this | view in chronology ]
Re: huh 'page not found'?
[ link to this | view in chronology ]
Re: huh 'page not found'?
[ link to this | view in chronology ]
Re: huh 'page not found'?
[ link to this | view in chronology ]
Re: huh 'page not found'?
update your bind server to turn all requests which return the IP address of sitefinder to return NXDOMAIN instead. Restores "correct" behavior. More difficult to implement.
Hack version 2:
Have a local override for the IP address of sitefinder which actually points at your own service or google. Trivial (I think) to implement.
Personally, I'm still impressed with the number of referrals I've been getting from sitefinder. Currently, its third behind Google and Yahoo.
Brandon
[ link to this | view in chronology ]
To stop this
[ link to this | view in chronology ]
Re: To stop this
[ link to this | view in chronology ]