Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dns lookup explanation made better #2476

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

dns lookup explanation made better #2476

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -208,7 +208,11 @@ Check HSTS list

DNS lookup
----------

* Before your computer can contact google.com, it needs to translate that domain name into an IP address, which is the numerical address computers use to find each other on the internet. This translation process is called a DNS lookup.
*Two Levels of Caching for Speed:
* Your computer leverages two layers of caching to speed up DNS lookups:
- Browser DNS Cache: Your web browser (Chrome, Firefox, Safari, etc.) maintains its own cache of recently resolved domain names. This is the first place your browser checks for the IP address of google.com.
- Operating System DNS Cache: If the browser's cache doesn't have an entry for google.com, your operating system (Windows, macOS, Linux) steps in. The OS has its own DNS resolver, which maintains a larger cache.
* Browser checks if the domain is in its cache. (to see the DNS Cache in
Chrome, go to `chrome://net-internals/#dns <chrome://net-internals/#dns>`_).
* If not found, the browser calls ``gethostbyname`` library function (varies by
Expand Down