{
  "id": 2592327,
  "title": "DNS, HTTP/1.1, HTTP/2, HTTP/3, CORS — A Beginner's Deep Dive",
  "url": "https://urgent.news/2026/08/22/dns-http-1-1-http-2-http-3-cors-a-beginners-deep-dive",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-22T14:49:18.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/dharam_in/dns-http11-http2-http3-cors-a-beginners-deep-dive-28h6"
  },
  "original_language": "en",
  "account": "The Domain Name System (DNS) is a crucial system that translates human-readable domain names into IP addresses that computers can understand. Every server has an IP address, and each website is hosted on a server. To access a website, we need its IP address, but IP addresses are not user-friendly. The DNS hierarchy consists of four layers: Root (.), Top-Level Domains (TLDs, e.g., .com), Domain (example), and Subdomains (www). A recursive resolver is responsible for querying the DNS hierarchy to resolve IP addresses for a given domain name.\n\nWhen a domain name is entered in a browser, the system first adds a dot (.) at the end of the domain and checks the IP in the cache. If the IP is found, it is returned to the browser. If not, the request goes to the ISP/Public DNS, which checks its cache. If the IP is still not found, the request proceeds to the root level servers, then the TLDs, and finally, the authoritative nameserver to find the IP address. Once the IP address is obtained, it is returned to the browser, and the ISP/Public DNS stores it in the cache for future use.\n\nDNS record types include A (IPv4), AAAA (IPv6), CNAME (subdomain and domain aliasing), MX (mail-related), TXT (arbitrary text data, such as domain verification and SPF records), and more. DNS record management allows for controlling various aspects of a domain, such as subdomains, IP addresses (both IPv4 and IPv6), email, and other configurations. Each record type has its own set of rules.\n\nNegative caching occurs when a non-existent domain is encountered in the DNS, and the DNS cache stores a negative response (NXDOMAIN) for that domain. This allows future queries for the same non-existent domain to bypass the entire DNS resolution process, saving time. The reason DNS changes do not propagate instantly across the internet is due to DNS propagation, which is the time it takes for updated DNS information to be replicated across the various servers worldwide. This process can take some time, leading to inconsistent IP addresses for the same domain name.\n\nDNS privacy concerns arise because DNS requests are not encrypted, making it possible for anyone to observe these requests and potentially track user activity. This issue is addressed through DNS over TLS (DoT) and DNS over HTTPS (DoH). DoT encrypts DNS requests using the TLS protocol, while DoH encrypts DNS requests as if they were standard HTTPS requests, using port 443. DoT uses port 853, and DoH also uses port 443.",
  "summary": "What is DNS and why we need it? DNS stand for Domain Name System, and it's main job is to translate domain name into IP. Think like every server has an IP and each website host on server so to get access of website we need the IP that look like this 192.168.10.10 (this is just for example) but IPs are not human friendly so we created the domain for that like example.com but the problem is the…",
  "key_points": [
    "DNS translates domain names to IP addresses for computer understanding",
    "DNS hierarchy has four layers: Root, TLDs, Domain, Subdomains",
    "DNS privacy concerns addressed via DNS over TLS (DoT) and HTTPS (DoH)"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}