3 ms·
Unfortunately I can't get to the new site (without changing my DNS servers) because Verizon is resolving krebsonsecurity.com to loopback. Presumably doing it fo
by mkopinsky 10y ago
Unfortunately I can't get to the new site (without changing my DNS servers) because Verizon is resolving krebsonsecurity.com to loopback. Presumably doing it for (poor) DDOS mitigation, but this sort of censorship is ridiculous.
$ nslookup krebsonsecurity.com 71.242.0.12
Server: 71.242.0.12
Address: 71.242.0.12#53
Non-authoritative answer:
Name: krebsonsecurity.com
Address: 127.0.0.1
EDIT: I see downthread that this is a DNS propagation issue. Nevermind.
- cesarb 10y agoThe krebsonsecurity.com site was really pointed to 127.0.0.1 by its owner recently (see https://twitter.com/briankrebs/status/779144394360381440 https://twitter.com/briankrebs/status/779144394360381440), so it's probably just a DNS cache at Verizon which hasn't expired yet. Give it some time.
- gipsies 10y agoA wild claim without any source. The owner set the IP to localhost himself. https://twitter.com/briankrebs/status/779144394360381440 https://twitter.com/briankrebs/status/779144394360381440
- mkopinsky 10y agoWhile 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.