Dns resolving
- 主要言語
- 言語のデータがありません
- スター
- 43.3k
- フォーク
- 5.7k
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
https://github.com/alex/what-happens-when#dns-lookup
I will like more explanations on this, for example, here http://unix.stackexchange.com/questions/122139/debian-cannot-resolve-hostnames it seems that point 3 of that is false since it do it before or at all only in certain cases defined by the /etc/reslov.conf also it seems "localhost" keyword is defined there, in /etc/hosts, but i can't define other words...do you know why?
A good thing to add to that part is this https://gist.github.com/Glamdring/6c96bd23d428dd1218ec62a1331900bf basically you never use chrome://net-internals/#dns since ttl is around 5 minutes, also http://stackoverflow.com/questions/9740822/how-long-does-google-chrome-cache-a-resource-if-expires-and-or-no-cache-headers seems chrome hardcode max 300 seconds anyway, and [here](http://stackoverflow.com/questions/11020027/dns-caching-in-linux) is says linux dns caching (nscd) is no enabled by default...
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
評価
この issue はまだ評価されていません。