<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Internet on Opslifeuk Limited</title><link>https://opslife.co.uk/tags/internet/</link><description>Recent content in Internet on Opslifeuk Limited</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sun, 05 Jul 2020 21:12:43 +0100</lastBuildDate><atom:link href="https://opslife.co.uk/tags/internet/index.xml" rel="self" type="application/rss+xml"/><item><title>How does the browser resolve DNS?</title><link>https://opslife.co.uk/general/dns/</link><pubDate>Sun, 05 Jul 2020 21:12:43 +0100</pubDate><guid>https://opslife.co.uk/general/dns/</guid><description>&lt;p&gt;Have you ever wondered how your browser resolves a domain name when you hit &lt;code&gt;Enter&lt;/code&gt; on a URL? Here&amp;rsquo;s how it works, at a high level.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Your browser first looks in its own cache for the address. If it doesn&amp;rsquo;t find it, it checks the OS cache, and finally the ISP&amp;rsquo;s cache.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;If the name isn&amp;rsquo;t cached, the next step is the &lt;code&gt;/etc/hosts&lt;/code&gt; file. If there&amp;rsquo;s an &lt;code&gt;IP&lt;/code&gt; address there, the browser tries to load the page from that server.&lt;/p&gt;</description></item></channel></rss>