Skip to content

Domain, DNS, HTTPS

Mở đầu

Khi gõ google.com Enter, sau đó xảy ra gì? Hành động đơn giản đó chứa cả chuỗi cộng tác tinh vi: domain resolution → DNS query → TLS handshake encryption. Hiểu = must cho dev — quyết web access được không, data bị steal không.

Bạn sẽ học:

  • DNS principles: domain → IP
  • Record types: A, CNAME, MX, TXT
  • HTTPS mechanism: TLS handshake
  • Certificate: chain of trust
  • Security: sao HTTPS = baseline Web hiện đại
ChươngNội dung
1DNS resolution
2DNS records
3HTTPS + TLS
4Cert trust chain
5HTTP vs HTTPS

0. Toàn cảnh: từ domain → secure connection

Internet communication base IP (vd 142.250.80.46), nhưng người không nhớ số. → DNS = "phone book" Internet, dịch domain → IP.

Nhưng tìm server thôi chưa đủ. Communication plaintext = ai cũng eavesdrop, tamper được. HTTPS = HTTP + TLS encryption, đảm bảo confidentiality + integrity.

Visit web hoàn chỉnh

  1. Domain resolution: browser hỏi DNS "google.com IP gì?", DNS trả "142.250.80.46"
  2. TCP connect: browser + server TCP 3-way handshake
  3. TLS handshake: 2 bên negotiate encryption + verify cert + exchange key
  4. Encrypted comm: mọi HTTP data qua encrypted channel

1. DNS: "phone book" Internet

DNS (Domain Name System) như tra phonebook: biết name (domain), cần phone (IP). Nhưng "phonebook" Internet là layered distributed system.

🔍 DNS 解析过程模拟器

🌐
浏览器缓存
💻
操作系统缓存
🔄
递归解析器
🌍
根域名服务器
📂
TLD 服务器
🏠
权威 DNS 服务器
解析流程说明: 浏览器访问网站时,需要先将域名翻译成 IP 地址。这个过程会依次查询多级缓存和服务器,直到找到对应的 IP。

4 step DNS

  1. Browser cache: query local cache, đã visit → dùng cached IP
  2. Recursive resolver: cache miss → request đến ISP recursive resolver (8.8.8.8)
  3. Tier query: recursive resolver hỏi tuần tự Root → TLD (.com) → Authoritative (google.com)
  4. Return: authoritative trả IP cuối, recursive cache + return browser
TierServerJobQuantity
RootRoot ServerBiết TLD address13 global groups
TLDTLD ServerManage .com, .vn, .orgMỗi suffix 1 group
AuthoritativeAuthoritativeLưu DNS record domain cụ thểMỗi domain ≥2
RecursiveResolverThay user complete queryISP hoặc public DNS

2. DNS records

DNS không chỉ dịch domain → IP. Qua record type khác, control mail routing, redirect, service discovery.

📋 DNS 记录类型速查

AAddress 记录

将域名映射到一个 IPv4 地址。这是最常见的 DNS 记录类型,浏览器访问网站时最终需要的就是这条记录。

示例记录
example.com. IN A 93.184.216.34
常见用途
  • 网站域名指向服务器 IP
  • 子域名指向不同的服务器
  • 配合负载均衡返回多个 IP
小贴士: DNS 不只是把域名翻译成 IP,它还承载了邮件路由、域名验证、负载均衡等多种功能,全靠不同的记录类型来实现。
RecordUseExample
ADomain → IPv4example.com → 93.184.216.34
AAAADomain → IPv6example.com → 2606:2800:220:1:...
CNAMEDomain → domain khác (alias)www.example.com → example.com
MXMail serverexample.com → mail.example.com
TXTText infoSPF verify, domain ownership
NSAuthoritative serverexample.com → ns1.example.com

Real scenarios

  • Deploy site: add A record → server IP, hoặc CNAME → CDN
  • Setup email: MX → mail server, TXT cho SPF/DKIM chống spam
  • Verify domain ownership: cloud vendor yêu cầu add TXT cụ thể
  • Load balance: cùng domain multi A record, DNS round-robin

3. HTTPS + TLS: "bulletproof vest" cho data

HTTP plaintext = như postcard, postman (middleman) đọc nội dung tuỳ ý. HTTPS = HTTP + TLS (Transport Layer Security) layer encryption = nhét postcard vào sealed envelope.

TLS handshake = step key build secure connection: verify identity + negotiate key trước khi transmit data.

🤝 TLS 握手过程演示

💻
客户端(浏览器)
Client Hello
发送支持的 TLS 版本、加密套件列表、随机数
Server Hello
选定 TLS 版本、加密套件、服务器随机数
Certificate
服务器发送数字证书(含公钥)
Key Exchange
双方协商生成会话密钥
Finished
双方确认握手成功,开始加密通信
🖥️
服务器

TLS 1.3 handshake

  1. Client Hello: client send supported cipher list + random
  2. Server Hello: server choose cipher, return cert + random
  3. Cert verify: client verify server cert trust (CA signature, expiry, domain match)
  4. Key exchange: 2 bên qua ECDHE negotiate shared key (key không transmit qua network)
  5. Encrypted comm: data sau dùng symmetric key encrypt
FeatureTLS 1.2TLS 1.3
Handshake RTT2-RTT1-RTT (first) / 0-RTT (resume)
Key exchangeRSA hoặc ECDHEChỉ ECDHE (forward secrecy)
CipherHỗ trợ nhiều legacyChỉ secure cipher
PerformanceChậm hơnNhanh hơn

4. Certificate trust chain: sao tin web này?

TLS handshake step quan trọng nhất = "cert verify". Browser judge cert thật vs fake thế nào? Trả lời: certificate trust chain — system endorsement layer by layer.

🔗 证书信任链可视化

点击每一层证书,查看它的详细信息和在信任链中的角色。

🏛️
根证书(Root CA)
信任的起点
签发
🏢
中间证书(Intermediate CA)
信任的桥梁
签发
🌐
服务器证书(Server Certificate)
网站的身份证
🏛️根证书(Root CA)
签发者DigiCert Global Root G2(自签名)
有效期25 年(2013 - 2038)
密钥长度RSA 2048 位
存储位置操作系统 / 浏览器内置信任库
数量级全球约 150 个受信根证书
根证书是整个信任链的锚点。它由根证书颁发机构自签名,预装在操作系统和浏览器中。全球只有少数几十个根 CA,它们的安全性由严格的审计和物理安全措施保障。根 CA 的私钥通常存储在离线的硬件安全模块(HSM)中。
🔍 浏览器验证流程
1浏览器收到服务器证书,读取其签发者信息
2找到中间证书,用中间 CA 的公钥验证服务器证书的签名
3再用根 CA 的公钥验证中间证书的签名
4确认根证书在本地信任库中 → 整条链验证通过

3-tier cert

  1. Root Certificate (Root CA): signed bởi trusted CA, pre-installed OS + browser. Đây là "anchor" của trust.
  2. Intermediate CA: signed bởi Root CA, dùng sign end cert. Root không direct sign web cert vì security isolation.
  3. Leaf Certificate: cert web thực dùng, signed bởi intermediate CA, chứa domain + public key + expiry.
Cert typeVerify levelIssue speedUse
DV (Domain Validation)Chỉ verify domain ownershipPhútPersonal, blog
OV (Organization)Verify org identityVài ngàyEnterprise site
EV (Extended)Strict org verifyVài tuầnBanking, finance
WildcardCover mọi subdomainTheo typeMulti-subdomain

5. HTTP vs HTTPS: sao encryption = baseline?

2024, >95% web traffic global qua HTTPS. Chrome đánh dấu HTTP site "Not Secure", search engine giảm rank HTTP. HTTPS không còn "optional", mà baseline modern Web.

🔐 HTTP vs HTTPS 数据传输对比

💻
浏览器
原始数据
password=MySecret123&user=zhangsan
🔓 明文传输
🕵️
中间人可窃听
🖥️
服务器
对比项HTTPHTTPS
端口80443
数据加密无(明文传输)TLS 对称加密
身份验证CA 证书验证服务器身份
数据完整性无保障MAC 校验防篡改
SEO 影响搜索引擎降权搜索引擎优先收录
性能开销无额外开销TLS 握手增加约 1-2 RTT
DimHTTPHTTPS
Data transmissionPlaintext, eavesdrop đượcEncrypted, không eavesdrop
Identity verifyKhôngCó (cert verify server)
Data integrityKhông (tamper được)Có (tamper detected)
Port80443
SEO impactGiảm rankTăng rank
Browser display"Not Secure" warningLock icon

Free HTTPS cert

Let's Encrypt = CA miễn phí + tự động, mọi site bật HTTPS không cost. Combo Certbot = 1-click apply + auto renew. Đa số cloud platform + CDN cung cấp SSL free.


Tổng kết

Domain + DNS + HTTPS = 3 pillar Internet infrastructure. DNS giúp dùng tên thay vì số, HTTPS đảm bảo communication safe + reliable.

  1. DNS layered: Root → TLD → Authoritative, tier query, cache speedup
  2. Record types: A → IP, CNAME → alias, MX → mail, TXT → verify
  3. TLS handshake: cert verify + key negotiate, TLS 1.3 chỉ 1-RTT
  4. Cert chain: Root CA → Intermediate CA → Leaf cert
  5. HTTPS baseline: free cert (Let's Encrypt) cho encryption zero-barrier

2026 cho VN dev

  • DNS providers:
    • Cloudflare: free, fast nhất, DDoS protection
    • AWS Route 53: deep AWS integration
    • VN registrar: Mat Bao, P.A. Việt Nam, Nhân Hoà
  • TLS cert:
    • Let's Encrypt: free, auto renew, default cho 99%
    • ZeroSSL: alternative Let's Encrypt
    • Commercial CA: DigiCert, Sectigo cho EV banking
  • VN context:
    • VN domain .vn qua VNNIC, mất 2-3 ngày verify
    • HTTPS bắt buộc theo VN regulation cho e-commerce + banking
  • Modern security:
    • HTTP/3 + QUIC: faster TLS handshake
    • HSTS: force HTTPS, prevent downgrade attack
    • DNS-over-HTTPS (DoH): encrypt DNS query, privacy
    • Certificate Transparency: public log mọi cert, detect rogue

Tài liệu