{"id":78523,"date":"2025-10-08T03:56:28","date_gmt":"2025-10-08T03:56:28","guid":{"rendered":"http:\/\/bangla.sitestree.com\/?p=78523"},"modified":"2025-10-08T03:56:29","modified_gmt":"2025-10-08T03:56:29","slug":"understanding-dns-lookup-and-dig-command-output-a-complete-guide-with-examples","status":"publish","type":"post","link":"http:\/\/bangla.sitestree.com\/?p=78523","title":{"rendered":"Understanding DNS Lookup and dig Command Output \u2014 A Complete Guide with Examples"},"content":{"rendered":"\n<p><\/p>\n\n\n\n<p>REF: AI Tools\/ChatGPT<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">\ud83e\udde0 Understanding DNS Lookup and <code>dig<\/code> Command Output \u2014 A Complete Guide with Examples<\/h1>\n\n\n\n<p>If you\u2019ve ever used the internet, you\u2019ve used DNS \u2014 even if you didn\u2019t know it. The <strong>Domain Name System (DNS)<\/strong> converts human-friendly names like <code>www.example.com<\/code> into IP addresses like <code>93.184.216.34<\/code>.<br>Let\u2019s explore how a DNS lookup works using the <code>dig<\/code> command, and understand each section of the DNS response: header, question, answer, authority, additional, flags, and more.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udd0d DNS Lookup: <code>dig<\/code> Command Output<\/h2>\n\n\n\n<p>The <code>dig<\/code> (Domain Information Groper) command is one of the most powerful tools for testing and analyzing DNS lookups.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83e\udded Example Command<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig www.example.com\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83e\udde9 Typical Output (Explained)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>; &lt;&lt;&gt;&gt; DiG 9.18.1-1ubuntu1.3-Ubuntu &lt;&lt;&gt;&gt; www.example.com\n;; global options: +cmd\n\n;; Got answer:\n;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 12345\n;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3\n\n;; QUESTION SECTION:\n;www.example.com.           IN      A\n\n;; ANSWER SECTION:\nwww.example.com.    3600    IN      A       93.184.216.34\n\n;; AUTHORITY SECTION:\nexample.com.        172800  IN      NS      a.iana-servers.net.\nexample.com.        172800  IN      NS      b.iana-servers.net.\n\n;; ADDITIONAL SECTION:\na.iana-servers.net. 172800  IN      A       199.43.135.53\nb.iana-servers.net. 172800  IN      A       199.43.133.53\na.iana-servers.net. 172800  IN      AAAA    2001:500:8f::53\n\n;; Query time: 25 msec\n;; SERVER: 192.168.56.10#53(192.168.56.10)\n;; WHEN: Tue Oct 08 10:12:44 EDT 2025\n;; MSG SIZE  rcvd: 210\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83e\uddf1 Breakdown by Sections<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Section<\/strong><\/th><th><strong>Meaning<\/strong><\/th><th><strong>Example \/ Explanation<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>HEADER<\/strong><\/td><td>Metadata about the query and server response<\/td><td><code>status: NOERROR<\/code> \u2192 successful lookup. Flags show query type and recursion status.<\/td><\/tr><tr><td><strong>QUESTION SECTION<\/strong><\/td><td>What was asked<\/td><td><code>www.example.com. IN A<\/code> \u2192 asking for IPv4 address.<\/td><\/tr><tr><td><strong>ANSWER SECTION<\/strong><\/td><td>The direct answer<\/td><td><code>www.example.com. 3600 IN A 93.184.216.34<\/code> \u2192 host IP address.<\/td><\/tr><tr><td><strong>AUTHORITY SECTION<\/strong><\/td><td>Which servers are authoritative for the zone<\/td><td><code>example.com. IN NS a.iana-servers.net.<\/code><\/td><\/tr><tr><td><strong>ADDITIONAL SECTION<\/strong><\/td><td>Supplementary info (IPs of NS records)<\/td><td>Lists A and AAAA records of the name servers.<\/td><\/tr><tr><td><strong>FOOTER<\/strong><\/td><td>Timing, query server, and message size<\/td><td><code>SERVER: 192.168.56.10#53<\/code> shows which DNS server responded.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\u2699\ufe0f Dig Command Details<\/h2>\n\n\n\n<p>Sometimes your <code>dig<\/code> output might look different. This depends on options, configuration, or empty sections.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why You Might Not See All Sections<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Some dig versions suppress empty sections.<\/li>\n\n\n\n<li>A <code>.digrc<\/code> file might set defaults like <code>+short<\/code> or <code>+noall<\/code>.<\/li>\n\n\n\n<li>Flags like <code>+short<\/code> simplify the output.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">\u2705 Show All Sections Explicitly<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig www.example.com +noall +answer +authority +additional +comments\n<\/code><\/pre>\n\n\n\n<p>Or, for a recursive trace:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig www.example.com +trace\n<\/code><\/pre>\n\n\n\n<p>To check if <code>.digrc<\/code> is hiding sections:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cat ~\/.digrc\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udce6 Additional Section Explained<\/h2>\n\n\n\n<p>The <strong>Additional Section<\/strong> provides helpful data such as the <strong>IP addresses of the name servers<\/strong> listed in the Authority Section.<\/p>\n\n\n\n<p><strong>Example:<\/strong><\/p>\n\n\n\n<p>Authority Section:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>example.com.  IN  NS  a.iana-servers.net.\n<\/code><\/pre>\n\n\n\n<p>Additional Section:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>a.iana-servers.net. IN A 199.43.135.53\n<\/code><\/pre>\n\n\n\n<p>This saves time by avoiding another DNS lookup.<\/p>\n\n\n\n<p><strong>Command to show it:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig example.com +noall +answer +authority +additional +comments\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83e\udde9 DNS Message Structure<\/h2>\n\n\n\n<p>Every DNS message (query or response) has the same structure:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Header (12 bytes)<\/strong><\/li>\n\n\n\n<li><strong>Question Section<\/strong><\/li>\n\n\n\n<li><strong>Answer Section<\/strong><\/li>\n\n\n\n<li><strong>Authority Section<\/strong><\/li>\n\n\n\n<li><strong>Additional Section<\/strong><\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">DNS Header Format<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Size (bits)<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td>ID<\/td><td>16<\/td><td>Identifier to match queries and responses<\/td><\/tr><tr><td>Flags<\/td><td>16<\/td><td>Operation and response flags<\/td><\/tr><tr><td>QDCOUNT<\/td><td>16<\/td><td>Number of questions<\/td><\/tr><tr><td>ANCOUNT<\/td><td>16<\/td><td>Number of answers<\/td><\/tr><tr><td>NSCOUNT<\/td><td>16<\/td><td>Number of authority records<\/td><\/tr><tr><td>ARCOUNT<\/td><td>16<\/td><td>Number of additional records<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Example Header:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 12345\n;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udea9 DNS Flag Details<\/h2>\n\n\n\n<p>Flags define how the message behaves and what the result means.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Flag<\/strong><\/th><th><strong>Bit(s)<\/strong><\/th><th><strong>Meaning<\/strong><\/th><th><strong>Example<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>QR<\/strong><\/td><td>0<\/td><td>0 = Query, 1 = Response<\/td><td>Response has QR=1<\/td><\/tr><tr><td><strong>Opcode<\/strong><\/td><td>1\u20134<\/td><td>Query type<\/td><td>Usually 0 = standard<\/td><\/tr><tr><td><strong>AA<\/strong><\/td><td>5<\/td><td>Authoritative Answer<\/td><td>Shown if reply is from the domain\u2019s own DNS<\/td><\/tr><tr><td><strong>TC<\/strong><\/td><td>6<\/td><td>Truncated Message<\/td><td>Response too large for UDP<\/td><\/tr><tr><td><strong>RD<\/strong><\/td><td>7<\/td><td>Recursion Desired<\/td><td>Client requests recursion<\/td><\/tr><tr><td><strong>RA<\/strong><\/td><td>8<\/td><td>Recursion Available<\/td><td>Server supports recursion<\/td><\/tr><tr><td><strong>RCODE<\/strong><\/td><td>12\u201315<\/td><td>Response Code<\/td><td>0 = No Error, 3 = NXDOMAIN<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Example from <code>dig<\/code>:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>;; flags: qr rd ra; status: NOERROR\n<\/code><\/pre>\n\n\n\n<p>Meaning:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>qr<\/code>: this is a response<\/li>\n\n\n\n<li><code>rd<\/code>: recursion desired<\/li>\n\n\n\n<li><code>ra<\/code>: recursion available<\/li>\n\n\n\n<li><code>NOERROR<\/code>: successful query<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udce6 Encapsulation in DNS<\/h2>\n\n\n\n<p>Encapsulation means wrapping one protocol\u2019s data inside another as it moves through network layers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Layer-by-Layer Breakdown<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Layer<\/strong><\/th><th><strong>Protocol<\/strong><\/th><th><strong>Encapsulated Data<\/strong><\/th><th><strong>Example<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Application<\/td><td>DNS<\/td><td>DNS Query\/Response<\/td><td>\u201cWhat is IP of <a href=\"http:\/\/www.example.com\/?%E2%80%9D\">www.example.com?\u201d<\/a><\/td><\/tr><tr><td>Transport<\/td><td>UDP or TCP<\/td><td>DNS Message<\/td><td>UDP Port 53<\/td><\/tr><tr><td>Network<\/td><td>IP<\/td><td>UDP Segment<\/td><td>Source: 192.168.1.2 \u2192 Dest: 8.8.8.8<\/td><\/tr><tr><td>Data Link<\/td><td>Ethernet<\/td><td>IP Packet<\/td><td>MAC to MAC transfer<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Visual Stack:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>+-----------------------------+\n| DNS Message (Header + Data) |\n+-----------------------------+\n| UDP Header (Port 53)        |\n+-----------------------------+\n| IP Header                   |\n+-----------------------------+\n| Ethernet Frame              |\n+-----------------------------+\n<\/code><\/pre>\n\n\n\n<p>Most queries use <strong>UDP port 53<\/strong>, while <strong>TCP port 53<\/strong> is used for large responses (like DNSSEC or zone transfers).<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83e\uddfe Dig Diagnostic Data (Not Header)<\/h2>\n\n\n\n<p>When you run <code>dig<\/code>, the first two lines are <strong>diagnostic<\/strong>, not part of the DNS message.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>; &lt;&lt;&gt;&gt; DiG 9.18.1-1ubuntu1.3-Ubuntu &lt;&lt;&gt;&gt; www.example.com\n;; global options: +cmd\n<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Line<\/strong><\/th><th><strong>Source<\/strong><\/th><th><strong>Part of DNS Message?<\/strong><\/th><\/tr><\/thead><tbody><tr><td><code>; &lt;&lt;&gt;&gt; DiG ... &lt;&lt;&gt;&gt;<\/code><\/td><td><code>dig<\/code> program banner<\/td><td>\u274c No<\/td><\/tr><tr><td><code>;; global options:<\/code><\/td><td>Local configuration<\/td><td>\u274c No<\/td><\/tr><tr><td><code>;; -&gt;&gt;HEADER&lt;&lt;- ...<\/code><\/td><td>Actual DNS message header<\/td><td>\u2705 Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\u2753 Question Section Data<\/h2>\n\n\n\n<p>The <strong>Question Section<\/strong> specifies what the client is asking for.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Field<\/strong><\/th><th><strong>Description<\/strong><\/th><th><strong>Example<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>QNAME<\/strong><\/td><td>Domain name requested<\/td><td><code>www.example.com<\/code><\/td><\/tr><tr><td><strong>QTYPE<\/strong><\/td><td>Record type<\/td><td><code>A<\/code> (IPv4 address)<\/td><\/tr><tr><td><strong>QCLASS<\/strong><\/td><td>Usually <code>IN<\/code> (Internet)<\/td><td><code>IN<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Example from dig:<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>;; QUESTION SECTION:\n;www.example.com.          IN      A\n<\/code><\/pre>\n\n\n\n<p>This means:<br>\u201cThe client is asking for the IPv4 address (A record) of <a href=\"http:\/\/www.example.com.xn--ivg\/\">www.example.com.\u201d<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83d\udcd8 Resource Records (RRs)<\/h2>\n\n\n\n<p>A <strong>Resource Record<\/strong> is the building block of DNS data \u2014 it contains a single piece of information about a domain.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Structure of a Resource Record<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Description<\/th><th>Example<\/th><\/tr><\/thead><tbody><tr><td><strong>NAME<\/strong><\/td><td>The domain name<\/td><td><code>www.example.com.<\/code><\/td><\/tr><tr><td><strong>TYPE<\/strong><\/td><td>Type of record (A, MX, NS, etc.)<\/td><td><code>A<\/code><\/td><\/tr><tr><td><strong>CLASS<\/strong><\/td><td>Usually IN (Internet)<\/td><td><code>IN<\/code><\/td><\/tr><tr><td><strong>TTL<\/strong><\/td><td>Time to Live (cache duration)<\/td><td><code>3600<\/code><\/td><\/tr><tr><td><strong>RDATA<\/strong><\/td><td>The actual data (depends on type)<\/td><td><code>93.184.216.34<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Example<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>NAME<\/th><th>TYPE<\/th><th>CLASS<\/th><th>TTL<\/th><th>RDATA<\/th><\/tr><\/thead><tbody><tr><td><a href=\"http:\/\/www.example.com\/\">www.example.com<\/a><\/td><td>A<\/td><td>IN<\/td><td>3600<\/td><td>93.184.216.34<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>Sections Containing RRs:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Answer Section<\/strong> \u2013 Direct answers.<\/li>\n\n\n\n<li><strong>Authority Section<\/strong> \u2013 Authoritative servers.<\/li>\n\n\n\n<li><strong>Additional Section<\/strong> \u2013 Supporting data like IPs of NS servers.<\/li>\n<\/ol>\n\n\n\n<p>\ud83d\udca1 <strong>In short:<\/strong><br>A Resource Record is a fact about a domain \u2014 and every DNS answer you receive is made up of one or more RRs.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">\ud83e\udded Summary<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Concept<\/strong><\/th><th><strong>Purpose<\/strong><\/th><\/tr><\/thead><tbody><tr><td>DNS Lookup<\/td><td>Converts domain names to IP addresses<\/td><\/tr><tr><td>Dig Tool<\/td><td>Displays DNS message details<\/td><\/tr><tr><td>Header<\/td><td>Metadata and flags<\/td><\/tr><tr><td>Question Section<\/td><td>The query being asked<\/td><\/tr><tr><td>Answer Section<\/td><td>The actual result<\/td><\/tr><tr><td>Authority Section<\/td><td>References to authoritative servers<\/td><\/tr><tr><td>Additional Section<\/td><td>Helpful extra data (e.g., NS IPs)<\/td><\/tr><tr><td>Resource Records<\/td><td>Core data units of DNS<\/td><\/tr><tr><td>Encapsulation<\/td><td>How DNS travels across network layers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">\u2728 Final Thought<\/h3>\n\n\n\n<p>Next time you run <code>dig www.example.com<\/code>, you\u2019re not just seeing text \u2014 you\u2019re watching a complete, multi-layered exchange between your computer and the world\u2019s DNS infrastructure.<br>Understanding these sections gives you the power to troubleshoot, teach, or secure networks with confidence.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p>&#8220;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>REF: AI Tools\/ChatGPT \ud83e\udde0 Understanding DNS Lookup and dig Command Output \u2014 A Complete Guide with Examples If you\u2019ve ever used the internet, you\u2019ve used DNS \u2014 even if you didn\u2019t know it. The Domain Name System (DNS) converts human-friendly names like www.example.com into IP addresses like 93.184.216.34.Let\u2019s explore how a DNS lookup works using &hellip; <\/p>\n<p><a class=\"more-link btn\" href=\"http:\/\/bangla.sitestree.com\/?p=78523\">Continue reading<\/a><\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-78523","post","type-post","status-publish","format-standard","hentry","category-root","item-wrap"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":78485,"url":"http:\/\/bangla.sitestree.com\/?p=78485","url_meta":{"origin":78523,"position":0},"title":"How an IP Address Gets Resolved to a Name in DNS","author":"Sayed","date":"September 13, 2025","format":false,"excerpt":"REF: AI Tools\/OpenAI\/ChatGPT Great question \ud83d\udc4d \u2014 let\u2019s turn this into a blog-ready, copyright-free post explaining step by step how an IP address gets resolved to a name (reverse lookup) and how the DNS servers, root servers, and TLD servers take part. How an IP Address Gets Resolved to a\u2026","rel":"","context":"In &quot;Computer Networks&quot;","block_context":{"text":"Computer Networks","link":"http:\/\/bangla.sitestree.com\/?cat=1978"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bangla.sitestree.com\/wp-content\/uploads\/2025\/09\/image-8.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":78478,"url":"http:\/\/bangla.sitestree.com\/?p=78478","url_meta":{"origin":78523,"position":1},"title":"Understanding DNS Root Servers: The Internet\u2019s Ultimate Directory","author":"Sayed","date":"September 13, 2025","format":false,"excerpt":"Ref: AI Tools\/OpenAI\/ChatGPT The Domain Name System (DNS) is how computers translate human-friendly names like www.example.com into IP addresses. At the very top of this system are the root servers \u2014 the backbone of DNS. What Are Root Servers? Root servers are special DNS servers that sit at the top\u2026","rel":"","context":"In &quot;Computer Networks&quot;","block_context":{"text":"Computer Networks","link":"http:\/\/bangla.sitestree.com\/?cat=1978"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":78488,"url":"http:\/\/bangla.sitestree.com\/?p=78488","url_meta":{"origin":78523,"position":2},"title":"DNS Caching Explained: How It Works, Pros, and Cons","author":"Sayed","date":"September 14, 2025","format":false,"excerpt":"Ref: AI Tools\/OpenAI\/ChatGPT (posted as is) \" Absolutely \ud83d\udc4d \u2014 here\u2019s a blog-ready, copyright-free post on DNS caching with explanation, how it works, pros, and cons. DNS Caching Explained: How It Works, Pros, and Cons When you visit a website like www.example.com, your computer asks the Domain Name System (DNS)\u2026","rel":"","context":"In &quot;Computer Networks&quot;","block_context":{"text":"Computer Networks","link":"http:\/\/bangla.sitestree.com\/?cat=1978"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bangla.sitestree.com\/wp-content\/uploads\/2025\/09\/image-9.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":78482,"url":"http:\/\/bangla.sitestree.com\/?p=78482","url_meta":{"origin":78523,"position":3},"title":"Understanding DNS on the Internet: Generic, Country, and Inverse Domains","author":"Sayed","date":"September 13, 2025","format":false,"excerpt":"Ref: AI Tools\/OpenAI\/ChatGPT Got it \ud83d\udc4d \u2014 here\u2019s a blog-ready, copyright-free article explaining DNS on the Internet, including generic domains, country domains, and the inverse domain. Understanding DNS on the Internet: Generic, Country, and Inverse Domains The Domain Name System (DNS) is often called the \u201cphonebook of the Internet.\u201d It\u2026","rel":"","context":"In &quot;Computer Networks&quot;","block_context":{"text":"Computer Networks","link":"http:\/\/bangla.sitestree.com\/?cat=1978"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bangla.sitestree.com\/wp-content\/uploads\/2025\/09\/image-7.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":78495,"url":"http:\/\/bangla.sitestree.com\/?p=78495","url_meta":{"origin":78523,"position":4},"title":"Who Resolves DNS Queries: ISP, Resolver, or Your PC?","author":"Sayed","date":"September 14, 2025","format":false,"excerpt":"Great question \ud83d\udc4c \u2014 this gets into the roles of DNS components in the real world. Let\u2019s break it down clearly, blog-ready and copyright-free: Who Resolves DNS Queries: ISP, Resolver, or Your PC? When you sit at home and connect to the internet through your ISP, different systems can play\u2026","rel":"","context":"In &quot;Computer Networks&quot;","block_context":{"text":"Computer Networks","link":"http:\/\/bangla.sitestree.com\/?cat=1978"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":22855,"url":"http:\/\/bangla.sitestree.com\/?p=22855","url_meta":{"origin":78523,"position":5},"title":"DNS A Records and CNAME Records in Practice #Root #By Sayed Ahmed","author":"Author-Check- Article-or-Video","date":"March 21, 2021","format":false,"excerpt":"Zone File Records The information as given below in a table are from a real domain and hosting. I just replaced the actual domain name with sahmed.com The domain is originally purchased at godaddy.com, and I created a hosting account for that domain (a real hosting account - not an\u2026","rel":"","context":"In &quot;FromSitesTree.com&quot;","block_context":{"text":"FromSitesTree.com","link":"http:\/\/bangla.sitestree.com\/?cat=1917"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts\/78523","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=78523"}],"version-history":[{"count":1,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts\/78523\/revisions"}],"predecessor-version":[{"id":78524,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=\/wp\/v2\/posts\/78523\/revisions\/78524"}],"wp:attachment":[{"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=78523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=78523"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/bangla.sitestree.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=78523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}