381–390 of 721 posts
So I had hardcoded my DNS server to googles, aka: dig @8.8.4.4 github.com +short I was not getting an answer. However using my routers/dhcp/ISP to set my DNS server, I am able to get answers: dig github.com +short 192.30.253.112
dig +trace github.com
Earlier quoted context omitted.
I'm surprised; I would have thought such large sites would use more than one DNS provider? I mean: $ host -t NS twitter.com twitter.com name server ns4.p34.dynect.net. twitter.com name server ns3.p34.dynect.net. twitter.com name server ns2.p34.dynect.net. twitter.com name server ns1.p34.dynect.net. I would have expected at least one of those to be somewhere else. What is the reason they would not have a backup provid…
I know a lot about some things, but almost nothing about networking, so excuse me if this is a really dumb question but - would your physical location determine what hosts you returned from that query? Like if you were in Asia would you get different ones back?
Switch to OpenDNS servers - 208.67.222.222 and 208.67.220.220. Even google NS are down it seems. Heroku works after switching to opendns.
Switch to OpenDNS servers - 208.67.222.222 and 208.67.220.220. Even google NS are down it seems. Heroku works after switching to opendns.
OpenDNS works because, as another poster notes, that, for better or worse, they don't strictly obey TTLs: https://news.ycombinator.com/item?id=12762429
Out of curiosity, why do caching DNS resolvers, such as the DNS resolver I run on my home network, not provide an option to retain last-known-good resolutions beyond the authority-provided time to live? In such a configuration, after the TTL expiration, the resolver would attempt to refresh from the authority/upstream provider, but if that attempt fails, the response would be a more graceful failure of returning a la…
Don't want to say much more due to it being my job, and I don't want to give away too much.
> ....point your machine or router's DNS to use opendns resolvers instead of your regular ones: 208.67.222.222 and 208.67.220.220
Earlier quoted context omitted.
Presumably with something like `dig @208.67.220.220 -t CNAME .herokussl.com`. This uses the OpenDNS nameservers, that people have been reporting as working. Haven't tested it as I am on the go.
thanks! figured it out but appreciate the help!!
Earlier quoted context omitted.
One possible issue is that IPs are re-used in cloud environments. Potentially, your browser could POST sensitive data to an IP address that now belongs to a totally different company.
Yeah, that is definitely possible. I mean, hopefully it is over HTTPS so they can't do anything with it... but if it isn't then it can definitely happen. Our servers get random web traffic all of the time.