top | item 12575475 (no title) gipsies | 9 years ago A wild claim without any source. The owner set the IP to localhost himself.https://twitter.com/briankrebs/status/779144394360381440 discuss order hn newest mkopinsky|9 years ago While in this case I was wrong, DNS poisoning is certainly not out of the realm of what Verizon will do, and when a site resolves properly on one ISP and not another, I don't think it's a "wild claim" to assume that it's the ISP's fault.
mkopinsky|9 years ago While in this case I was wrong, DNS poisoning is certainly not out of the realm of what Verizon will do, and when a site resolves properly on one ISP and not another, I don't think it's a "wild claim" to assume that it's the ISP's fault.
mkopinsky|9 years ago