[{"data":1,"prerenderedAt":658},["ShallowReactive",2],{"navigation_docs":3,"-network-dns-cname-vs-a-record-guide":352,"-network-dns-cname-vs-a-record-guide-surround":653},[4,54,83,116,125,161,179,200],{"title":5,"path":6,"stem":7,"children":8},"Ai","/ai","ai",[9,12,42,46,50],{"title":10,"path":6,"stem":11},"AI 技術探索","ai/index",{"title":13,"path":14,"stem":15,"children":16,"page":41},"Rag","/ai/rag","ai/RAG",[17,21,25,29,33,37],{"title":18,"path":19,"stem":20},"BM25 演算法深入解析：從 TF-IDF 到現代搜尋引擎的核心技術","/ai/rag/bm25-deep-dive-from-tf-idf-to-rag","ai/RAG/bm25-deep-dive-from-tf-idf-to-rag",{"title":22,"path":23,"stem":24},"Dense Retrieval（向量檢索）深入解析","/ai/rag/dense-retrieval-deep-dive","ai/RAG/dense-retrieval-deep-dive",{"title":26,"path":27,"stem":28},"RAG（Retrieval-Augmented Generation）原理與實作入門","/ai/rag/rag-intro-principles-and-implementation","ai/RAG/rag-intro-principles-and-implementation",{"title":30,"path":31,"stem":32},"RAG Retrieval Strategy 深入解析","/ai/rag/rag-retrieval-strategy-deep-dive","ai/RAG/rag-retrieval-strategy-deep-dive",{"title":34,"path":35,"stem":36},"Reciprocal Rank Fusion（RRF）教學：打造更穩定的檢索融合策略","/ai/rag/rrf-reciprocal-rank-fusion-guide","ai/RAG/rrf-reciprocal-rank-fusion-guide",{"title":38,"path":39,"stem":40},"TF-IDF（Term Frequency–Inverse Document Frequency）深入解析","/ai/rag/tf-idf-deep-dive","ai/RAG/tf-idf-deep-dive",false,{"title":43,"path":44,"stem":45},"Docus AI 功能完整實作指南","/ai/docus-ai-implementation","ai/docus-ai-implementation",{"title":47,"path":48,"stem":49},"llms.txt 是什麼？在 Nuxt 中控制 AI 與搜尋引擎爬蟲的新方式","/ai/llms-txt","ai/llms-txt",{"title":51,"path":52,"stem":53},"MCP（Model Context Protocol）是什麼？用「AI 的 USB-C」理解模型如何安全連接工具與資料","/ai/mcp_concept","ai/mcp_concept",{"title":55,"path":56,"stem":57,"children":58,"page":41},"Data Analysis","/data-analysis","data-analysis",[59,63,67,71,75,79],{"title":60,"path":61,"stem":62},"Exploratory Data Analysis（EDA）資料探索分析入門","/data-analysis/exploratory-data-analysis-eda","data-analysis/exploratory-data-analysis-eda",{"title":64,"path":65,"stem":66},"PR-AUC 深入解析：不平衡分類問題的重要評估指標","/data-analysis/pr-auc-for-imbalanced-classification","data-analysis/pr-auc-for-imbalanced-classification",{"title":68,"path":69,"stem":70},"ROC-AUC 深入解析：理解分類模型的判斷能力","/data-analysis/roc-auc-complete-guide","data-analysis/roc-auc-complete-guide",{"title":72,"path":73,"stem":74},"SHAP（SHapley Additive exPlanations）模型解釋方法深入解析","/data-analysis/shap-model-interpretation-complete-guide","data-analysis/shap-model-interpretation-complete-guide",{"title":76,"path":77,"stem":78},"Social Network Analysis（SNA）深入解析","/data-analysis/social-network-analysis-sna","data-analysis/social-network-analysis-sna",{"title":80,"path":81,"stem":82},"Time-based Split：為什麼時間序列資料不能使用 Random Split？","/data-analysis/time-based-split-vs-random-split","data-analysis/time-based-split-vs-random-split",{"title":84,"path":85,"stem":86,"children":87,"page":41},"MachineLearning","/machine_learning","machine_learning",[88,92,96,100,104,108,112],{"title":89,"path":90,"stem":91},"Confusion Matrix（混淆矩陣）完整解析","/machine_learning/confusion-matrix","machine_learning/confusion-matrix",{"title":93,"path":94,"stem":95},"Decision Tree 模型完整教學：從原理到 Python 實作","/machine_learning/decision-tree-complete-guide","machine_learning/decision-tree-complete-guide",{"title":97,"path":98,"stem":99},"為什麼 Decision Tree 在 Tabular Data 上常常勝過 Deep Learning？","/machine_learning/decision-tree-vs-deep-learning-on-tabular-data","machine_learning/decision-tree-vs-deep-learning-on-tabular-data",{"title":101,"path":102,"stem":103},"LightGBM 模型入門：理解高效能的 Gradient Boosting 演算法","/machine_learning/lightgbm-intro-for-tabular-data","machine_learning/lightgbm-intro-for-tabular-data",{"title":105,"path":106,"stem":107},"Logistic Regression（Logit 回歸）完整教學","/machine_learning/logistic-regression-complete-guide","machine_learning/logistic-regression-complete-guide",{"title":109,"path":110,"stem":111},"為什麼模型訓練需要 Train / Validation / Test Dataset？","/machine_learning/train-validation-test-dataset","machine_learning/train-validation-test-dataset",{"title":113,"path":114,"stem":115},"XGBoost 原理與實務教學","/machine_learning/xgboost-complete-guide","machine_learning/xgboost-complete-guide",{"title":117,"path":118,"stem":119,"children":120,"page":41},"Network","/network","network",[121],{"title":122,"path":123,"stem":124},"DNS 設定入門：CNAME vs A Record 完整解析","/network/dns-cname-vs-a-record-guide","network/dns-cname-vs-a-record-guide",{"title":126,"path":127,"stem":128,"children":129},"Nuxt","/nuxt","nuxt",[130,133,137,141,145,149,153,157],{"title":131,"path":127,"stem":132},"Nuxt 實戰指南","nuxt/index",{"title":134,"path":135,"stem":136},"Abstraction Layer 與 Adapter 的差別，一次搞懂設計角色","/nuxt/adapter_abstraction_layer","nuxt/adapter_abstraction_layer",{"title":138,"path":139,"stem":140},"Nuxt 4 全面理解 — 專案檔案結構解析","/nuxt/directory_structure","nuxt/directory_structure",{"title":142,"path":143,"stem":144},"Nuxt 前端 build 流程完整解析","/nuxt/frontend_build","nuxt/frontend_build",{"title":146,"path":147,"stem":148},"Nitro 是什麼？從 Nuxt 專案到 Server 與 Edge 的關鍵引擎","/nuxt/nitro","nuxt/nitro",{"title":150,"path":151,"stem":152},"深入理解 Nuxt 的 .nuxt 與 .output：為什麼部署時一定要分清楚？","/nuxt/nuxt_and_output","nuxt/nuxt_and_output",{"title":154,"path":155,"stem":156},"Nuxt 中 dev、build、preview 的差異一次搞懂","/nuxt/nuxt_dev_build_preview","nuxt/nuxt_dev_build_preview",{"title":158,"path":159,"stem":160},"Nuxt Image vs \u003Cimg>：為什麼 Nuxt 3 專案幾乎都該用 \u003CNuxtImg>？","/nuxt/nuxt_image","nuxt/nuxt_image",{"title":162,"path":163,"stem":164,"children":165},"Python 程式開發","/python","python/index",[166,167,171,175],{"title":162,"path":163,"stem":164},{"title":168,"path":169,"stem":170},"如何在 FastAPI 中調用記憶體 Buffer 回傳圖片 (附實例)","/python/memory_buffer","python/memory_buffer",{"title":172,"path":173,"stem":174},"Python 單元測試教學：如何為你的程式撰寫 Test","/python/python-unit-testing-unittest-pytest","python/python-unit-testing-unittest-pytest",{"title":176,"path":177,"stem":178},"如何使用 uv 取代 pip：改善 Python 專案的開發流程","/python/uv","python/uv",{"title":180,"path":181,"stem":182,"children":183,"page":41},"Statistic","/statistic","statistic",[184,188,192,196],{"title":185,"path":186,"stem":187},"卡方檢定（Chi-Square Test）入門教學","/statistic/chi-square-test-intro","statistic/chi-square-test-intro",{"title":189,"path":190,"stem":191},"常見抽樣方法（Sampling Methods）教學：Stratified、Quota、Convenience、Systematic、Simple Random","/statistic/common-sampling-methods-guide","statistic/common-sampling-methods-guide",{"title":193,"path":194,"stem":195},"Cramér’s V 指標介紹：如何衡量兩個類別變數之間的關聯","/statistic/cramers-v-for-categorical-association","statistic/cramers-v-for-categorical-association",{"title":197,"path":198,"stem":199},"Mann–Whitney U 與 Kolmogorov–Smirnov（KS）檢定：非參數統計檢定的入門指南","/statistic/mann-whitney-u-and-ks-test-intro","statistic/mann-whitney-u-and-ks-test-intro",{"title":201,"path":202,"stem":203,"children":204},"WebDev","/web_dev","web_dev",[205,208,234,248,282,312,334],{"title":206,"path":202,"stem":207},"Web 前端開發","web_dev/index",{"title":209,"path":210,"stem":211,"children":212},"瀏覽器與渲染","/web_dev/browser","web_dev/browser/index",[213,214,218,222,226,230],{"title":209,"path":210,"stem":211},{"title":215,"path":216,"stem":217},"瀏覽器儲存空間完整解析：Cookie、localStorage、IndexedDB 到 Cache Storage","/web_dev/browser/browser-storage-comprehensive-guide","web_dev/browser/browser-storage-comprehensive-guide",{"title":219,"path":220,"stem":221},"DOM (Document Object Model) 深入解析","/web_dev/browser/dom","web_dev/browser/dom",{"title":223,"path":224,"stem":225},"Service Worker Request Flow 深入解析","/web_dev/browser/service-worker-request-flow","web_dev/browser/service-worker-request-flow",{"title":227,"path":228,"stem":229},"CSR、SSR 與 SSG 是什麼？前端渲染策略完整比較","/web_dev/browser/ssr_csr_ssg","web_dev/browser/ssr_csr_ssg",{"title":231,"path":232,"stem":233},"Virtual DOM 深入解析：為什麼它能優化前端效能？","/web_dev/browser/virtual_dom","web_dev/browser/virtual_dom",{"title":235,"path":236,"stem":237,"children":238},"圖形技術","/web_dev/graphics","web_dev/graphics/index",[239,240,244],{"title":235,"path":236,"stem":237},{"title":241,"path":242,"stem":243},"為什麼 Three.js 專案幾乎都選擇 CSR？從 SSR 問題談起","/web_dev/graphics/threejs_csr","web_dev/graphics/threejs_csr",{"title":245,"path":246,"stem":247},"WebGL 是什麼？為什麼前端 3D 幾乎都靠它？","/web_dev/graphics/webgl","web_dev/graphics/webGL",{"title":249,"path":250,"stem":251,"children":252},"架構與配置","/web_dev/infrastructure","web_dev/infrastructure/index",[253,254,258,262,266,270,274,278],{"title":249,"path":250,"stem":251},{"title":255,"path":256,"stem":257},"Zeabur + K3s + Nuxt 部署架構完整解析","/web_dev/infrastructure/k3s-zeabur","web_dev/infrastructure/K3s-zeabur",{"title":259,"path":260,"stem":261},"ECS vs Docker vs Kubernetes：從部署堆疊理解三層架構","/web_dev/infrastructure/ecs-docker-kubernetes-stack","web_dev/infrastructure/ecs-docker-kubernetes-stack",{"title":263,"path":264,"stem":265},"ECS vs VPS 是什麼？從部署網站的角度一次搞懂差別","/web_dev/infrastructure/ecs-vs-vps","web_dev/infrastructure/ecs-vs-vps",{"title":267,"path":268,"stem":269},"Zeabur 內網服務連線完整入門指南","/web_dev/infrastructure/k3s-internal-networking","web_dev/infrastructure/k3s-internal-networking",{"title":271,"path":272,"stem":273},"使用 Microservices 架構設計系統的優勢解析","/web_dev/infrastructure/microservices-architecture-advantages","web_dev/infrastructure/microservices-architecture-advantages",{"title":275,"path":276,"stem":277},"Nginx 入門教學：從反向代理到與 Kubernetes 的架構比較","/web_dev/infrastructure/nginx-intro","web_dev/infrastructure/nginx-intro",{"title":279,"path":280,"stem":281},"YAML 配置是什麼？為什麼現代開發都在用它","/web_dev/infrastructure/yaml-configuration","web_dev/infrastructure/yaml-configuration",{"title":283,"path":284,"stem":285,"children":286},"網絡與通訊","/web_dev/network","web_dev/network/index",[287,288,292,296,300,304,308],{"title":283,"path":284,"stem":285},{"title":289,"path":290,"stem":291},"HTTP Request 結構完整解析：從 Request Line 到 Header 一次看懂","/web_dev/network/http-request-structure","web_dev/network/http-request-structure",{"title":293,"path":294,"stem":295},"OSI 模型（Open Systems Interconnection Model）完整解析","/web_dev/network/osi-model","web_dev/network/osi-model",{"title":297,"path":298,"stem":299},"RESTful API 設計原則與實務解析","/web_dev/network/restful-api","web_dev/network/restful-api",{"title":301,"path":302,"stem":303},"RESTful API 五大設計原則深入解析","/web_dev/network/restful-api-principles","web_dev/network/restful-api-principles",{"title":305,"path":306,"stem":307},"Server-Sent Events (SSE) 深入解析與實作教學","/web_dev/network/sse-introduction","web_dev/network/sse-introduction",{"title":309,"path":310,"stem":311},"WebSocket 入門教學：從概念到 Node.js 實作","/web_dev/network/websocket-introduction","web_dev/network/websocket-introduction",{"title":313,"path":314,"stem":315,"children":316},"認證與安全","/web_dev/security","web_dev/security/index",[317,318,322,326,330],{"title":313,"path":314,"stem":315},{"title":319,"path":320,"stem":321},"使用 Cookie 與 Session 建立使用者驗證（完整新手教學）","/web_dev/security/cookie-session-authentication","web_dev/security/cookie-session-authentication",{"title":323,"path":324,"stem":325},"JWT 驗證機制完整解析：從登入流程到實務應用","/web_dev/security/jwt-authentication","web_dev/security/jwt-authentication",{"title":327,"path":328,"stem":329},"Secret Key 簽名是什麼？從零理解資料簽名的本質","/web_dev/security/secret-key-signing","web_dev/security/secret-key-signing",{"title":331,"path":332,"stem":333},"SSH（Secure Shell）是什麼？從遠端登入到安全通道的核心概念","/web_dev/security/ssh","web_dev/security/ssh",{"title":335,"path":336,"stem":337,"children":338},"SEO 與規範","/web_dev/seo","web_dev/seo/index",[339,340,344,348],{"title":335,"path":336,"stem":337},{"title":341,"path":342,"stem":343},"Canonical URL 是什麼？用生活化方式搞懂前端 SEO 的基本保命符","/web_dev/seo/canonical_link","web_dev/seo/canonical_link",{"title":345,"path":346,"stem":347},"robots.txt 是什麼？SEO 的第一道守門員","/web_dev/seo/robot_txt","web_dev/seo/robot_txt",{"title":349,"path":350,"stem":351},"Nuxt SEO 中的 Meta 與 SEO 工具是如何運作的？","/web_dev/seo/seo","web_dev/seo/seo",{"id":353,"title":122,"body":354,"description":640,"extension":641,"links":642,"meta":643,"navigation":650,"path":123,"seo":651,"stem":124,"__hash__":652},"docs/network/dns-cname-vs-a-record-guide.md",{"type":355,"value":356,"toc":627},"minimark",[357,362,366,378,381,385,388,391,393,397,400,403,419,425,428,430,434,437,439,448,459,462,464,468,471,474,477,479,483,489,492,508,511,513,516,519,534,537,540,542,545,548,551,554,557,559,562,565,575,578,580,583,586,589,591,594,623],[358,359,361],"h2",{"id":360},"為什麼你一定會碰到-dns","為什麼你一定會碰到 DNS？",[363,364,365],"p",{},"當你開始架設網站（例如使用 Vercel、Zeabur 或自架伺服器），第一個一定會遇到的問題就是：「我的網域要怎麼指到我的服務？」這個問題的核心，其實就是 DNS（Domain Name System）。",[363,367,368,369,373,374,377],{},"DNS 的角色可以理解為網路世界的「翻譯系統」。使用者輸入的是人類可讀的網域名稱，例如 ",[370,371,372],"code",{},"example.com","，但實際上網路通訊依賴的是 IP 位址，例如 ",[370,375,376],{},"192.168.1.1","。DNS 的工作，就是在這兩者之間建立對應關係，讓瀏覽器能夠找到正確的伺服器。",[379,380],"hr",{},[358,382,384],{"id":383},"dns-的基本運作流程","DNS 的基本運作流程",[363,386,387],{},"當使用者在瀏覽器輸入一個網址時，背後其實發生了一連串解析流程。首先，瀏覽器會向 DNS Server 查詢該網域對應的 IP 位址。DNS Server 回傳結果後，瀏覽器才會發起真正的 HTTP / HTTPS 請求。",[363,389,390],{},"這個過程看似簡單，但其實是整個網際網路能運作的基礎。若 DNS 設定錯誤，即使你的網站已經部署完成，使用者仍然無法正確連線。",[379,392],{},[358,394,396],{"id":395},"a-record-是什麼","A Record 是什麼？",[363,398,399],{},"A Record（Address Record）是 DNS 中最基本、也是最直接的一種記錄類型。它的功能是將一個網域名稱直接對應到一個 IP 位址。",[363,401,402],{},"例如：",[404,405,410],"pre",{"className":406,"code":407,"language":408,"meta":409,"style":409},"language-txt shiki shiki-themes github-dark","example.com → 192.168.1.1\n","txt","",[370,411,412],{"__ignoreMap":409},[413,414,417],"span",{"class":415,"line":416},"line",1,[413,418,407],{},[363,420,421,422,424],{},"這代表當使用者訪問 ",[370,423,372],{}," 時，DNS 會直接回傳該 IP 位址，瀏覽器便會與這台伺服器建立連線。",[363,426,427],{},"A Record 的特性在於「直接性」，它沒有中間轉換層，因此解析速度通常較快，且結構單純。但相對地，當伺服器 IP 發生變動時，就必須手動更新 DNS 設定，維護成本較高。",[379,429],{},[358,431,433],{"id":432},"cname-是什麼","CNAME 是什麼？",[363,435,436],{},"CNAME（Canonical Name Record）則提供了一種更具彈性的做法。它並不是直接對應 IP，而是將一個網域指向另一個網域名稱。",[363,438,402],{},[404,440,442],{"className":406,"code":441,"language":408,"meta":409,"style":409},"www.example.com → myapp.vercel.app\n",[370,443,444],{"__ignoreMap":409},[413,445,446],{"class":415,"line":416},[413,447,441],{},[363,449,450,451,454,455,458],{},"在這個情境中，當使用者訪問 ",[370,452,453],{},"www.example.com"," 時，DNS 會告訴瀏覽器「請改查詢 ",[370,456,457],{},"myapp.vercel.app","」，接著再解析該網域對應的 IP。",[363,460,461],{},"也就是說，CNAME 本質上是一種「別名機制」，它允許你把多個網域統一指向同一個服務來源，而不需要關心底層 IP 的變化。",[379,463],{},[358,465,467],{"id":466},"a-record-vs-cname-的核心差異","A Record vs CNAME 的核心差異",[363,469,470],{},"A Record 與 CNAME 的最大差異，在於「是否直接指向 IP」。",[363,472,473],{},"A Record 是一條直接連線，從網域名稱到 IP 位址只需要一次解析，因此在結構上最簡單，也最穩定。相對地，CNAME 則需要多一次解析過程，因為它會先指向另一個網域，再由該網域解析出 IP。",[363,475,476],{},"此外，CNAME 提供更高的彈性，特別適合用於現代雲端服務。像是 Vercel、Netlify 或 Zeabur 這類平台，其底層 IP 可能會隨著負載或架構調整而變動，使用 CNAME 可以避免頻繁修改 DNS 設定。",[379,478],{},[358,480,482],{"id":481},"為什麼-root-domain-通常不能用-cname","為什麼 root domain 通常不能用 CNAME？",[363,484,485,486,488],{},"在實務上，你會發現 ",[370,487,372],{},"（裸網域）通常無法設定為 CNAME。這是因為 DNS 規範要求 root domain 必須同時存在 SOA（Start of Authority）與 NS（Name Server）記錄，而 CNAME 會覆蓋整個節點，導致這些必要記錄無法共存。",[363,490,491],{},"因此，一般會採用以下策略：",[404,493,495],{"className":406,"code":494,"language":408,"meta":409,"style":409},"example.com → A Record\nwww.example.com → CNAME\n",[370,496,497,502],{"__ignoreMap":409},[413,498,499],{"class":415,"line":416},[413,500,501],{},"example.com → A Record\n",[413,503,505],{"class":415,"line":504},2,[413,506,507],{},"www.example.com → CNAME\n",[363,509,510],{},"這種配置同時兼顧了 DNS 規範與彈性需求。",[379,512],{},[358,514,515],{"id":515},"實務應用場景解析",[363,517,518],{},"在現代 Web 開發中，A Record 與 CNAME 往往會搭配使用。",[363,520,521,522,525,526,529,530,533],{},"當你使用雲端平台（例如 Vercel）部署前端網站時，通常會將子網域（如 ",[370,523,524],{},"www"," 或 ",[370,527,528],{},"blog","）設定為 CNAME，指向平台提供的網域，例如 ",[370,531,532],{},"cname.vercel-dns.com","。這樣做的好處是，即使平台底層 IP 發生變化，你的 DNS 設定仍然不需要修改。",[363,535,536],{},"另一方面，當你使用 VPS 或 Zeabur 部署後端服務，並且擁有固定 IP 時，就會使用 A Record 將主網域直接指向該 IP。",[363,538,539],{},"這種「root 用 A、子網域用 CNAME」的混合策略，是目前最常見且穩定的做法。",[379,541],{},[358,543,544],{"id":544},"常見錯誤與注意事項",[363,546,547],{},"在設定 DNS 時，有幾個常見錯誤需要特別注意。",[363,549,550],{},"首先，CNAME 只能指向「網域名稱」，不能直接指向 IP。如果將 CNAME 指向 IP，DNS 將無法正確解析。",[363,552,553],{},"其次，同一個網域名稱不能同時存在 A Record 與 CNAME，這會造成衝突並導致解析失敗。",[363,555,556],{},"最後，DNS 設定變更後不會立即生效，通常需要數分鐘到數小時不等，這個過程稱為 propagation。在測試設定時，應耐心等待或使用工具確認是否已更新。",[379,558],{},[358,560,561],{"id":561},"用一個直覺方式理解",[363,563,564],{},"如果把 DNS 想像成查地址的過程：",[566,567,568,572],"ul",{},[569,570,571],"li",{},"A Record 就像是直接告訴你「這個地方的實際地址」",[569,573,574],{},"CNAME 則像是告訴你「去問另一個人，他會給你地址」",[363,576,577],{},"這個差異，正好反映了兩者在設計上的核心理念：一個追求直接性，一個追求彈性。",[379,579],{},[358,581,582],{"id":582},"結論",[363,584,585],{},"A Record 與 CNAME 是 DNS 中最核心的兩種記錄類型。前者提供直接且穩定的 IP 對應方式，後者則提供靈活且可維護的網域映射機制。",[363,587,588],{},"在現代 Web 架構中，理解這兩者的差異與適用場景，是正確設定網域與部署服務的關鍵。只要掌握「A Record 指向 IP、CNAME 指向網域」這個核心原則，就能避免大部分常見錯誤，並建立穩定可靠的網站架構。",[379,590],{},[358,592,593],{"id":593},"參考資料",[595,596,597,605,611,617],"ol",{},[569,598,599],{},[600,601,602],"a",{"href":602,"rel":603},"https://www.cloudflare.com/learning/dns/dns-records/",[604],"nofollow",[569,606,607],{},[600,608,609],{"href":609,"rel":610},"https://vercel.com/docs/projects/domains",[604],[569,612,613],{},[600,614,615],{"href":615,"rel":616},"https://www.rfc-editor.org/rfc/rfc1034",[604],[569,618,619],{},[600,620,621],{"href":621,"rel":622},"https://www.rfc-editor.org/rfc/rfc1035",[604],[624,625,626],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":409,"searchDepth":504,"depth":504,"links":628},[629,630,631,632,633,634,635,636,637,638,639],{"id":360,"depth":504,"text":361},{"id":383,"depth":504,"text":384},{"id":395,"depth":504,"text":396},{"id":432,"depth":504,"text":433},{"id":466,"depth":504,"text":467},{"id":481,"depth":504,"text":482},{"id":515,"depth":504,"text":515},{"id":544,"depth":504,"text":544},{"id":561,"depth":504,"text":561},{"id":582,"depth":504,"text":582},{"id":593,"depth":504,"text":593},"從基礎概念到實務應用，深入理解 DNS 中 A Record 與 CNAME 的差異與使用情境。","md",null,{"tags":644,"category":119,"date":649},[645,646,647,648,203],"dns","cname","a-record","networking","2026-03-17",true,{"title":122,"description":640},"6NemL2n95vFobrulBeDikw-DZ2L0qGOygqQdv5MJsEY",[654,656],{"title":113,"path":114,"stem":115,"description":655,"children":-1},"從 Boosting 概念開始，深入理解 XGBoost 的運作原理，並透過實際案例了解如何使用 XGBoost 建立高效的機器學習模型。",{"title":131,"path":127,"stem":132,"description":657,"children":-1},"掌握 Nuxt.js 框架的各項功能，打造高效、流暢且具備視覺魅力的現代化 Web 應用。",1776690842410]