3 ms·
>KrebsOnSecurity is now up... It isn't for me. I get "This site can’t be reached - krebsonsecurity.com refused to connect."
by tim333 10y ago
>KrebsOnSecurity is now up...
It isn't for me. I get "This site can’t be reached - krebsonsecurity.com refused to connect."
- notimetorelax 10y agoLooks like redirect from naked domain to www.krebsonsecurity.com is missing. This seem to work better http://www.krebsonsecurity.com/ http://www.krebsonsecurity.com/
- semi-extrinsic 10y agoClicking your link doesn't work either for me (connection refused).
- dotancohen 10y ago$ dig www.krebsonsecurity.com | grep IN ;www.krebsonsecurity.com. IN A www.krebsonsecurity.com. 267 IN A 127.0.0.1
- wila 10y agoI see the same. But it is not uncommon for DNS as it needs time to propagate globally. FWIW, no inserting the www subdomain does not help either. Waiting will though. Edit: works here now
- neitsab 10y agoFor now DNS information reflect the former address and name servers for most people: $ dig krebsonsecurity.com +short 127.0.0.1 $ dig ns krebsonsecurity.com +short ns2.prolexic.net. ns1.prolexic.net. 127.0.0.1 points to localhost, which is your local machine. However if you query the Whois, you'll see that the site changed its name servers from Prolexic's to Google's ones today: $ whois krebsonsecurity.com | grep "Name Server" Name Server: NS-CLOUD-D1.GOOGLEDOMAINS.COM Name Server: NS-CLOUD-D2.GOOGLEDOMAINS.COM Name Server: NS-CLOUD-D3.GOOGLEDOMAINS.COM Name Server: NS-CLOUD-D4.GOOGLEDOMAINS.COM And indeed if we query those directly: $ dig krebsonsecurity.com @ns-cloud-d1.googledomains.com +short 130.211.45.45 Such name servers change can take up to 72h to propagate. Meanwhile, you can edit your /etc/hosts file (on GNU/Linux) to hardcode the IP of krebsonsecurity.com: # echo "130.211.45.45 krebsonsecurity.com" >> /etc/hosts (must run as root) Now browse to krebsonsecurity.com et voilà!
- jsjohnst 10y agoDNS doesn't "propagate" and it certainly doesn't take 72hrs either. You're simply waiting for the cache TTL to expire on the DNS server you are using, then it'll re-query the authoritative servers.
- johncolanduoni 10y agoWhat about that doesn't sound like propagation? I guess you could try and be pedantic and claim since there's no "push" it's not propagation, but this exact phenomena in DNS is called propagation all the time. Also many ISP's servers ignore TTLs for certain changes that happen infrequently (like NS changes) and wait a few days. So they might refresh the A record according to the TTL, but they'll still be pulling it from the wrong name server.
- jsjohnst 10y agoMore often than not, it's not ISPs ignoring TTLs as you describe, it is an improperly configured SOA record. There's more TTLs you (as owner of domain) control involved in the caching of a record than just the TTL on an A/AAAA record. As to your point about "propagation", argumentum ad populum applies.