import type { Metadata } from "next";
import Link from "next/link";
import { AdSlot } from "@/components/AdSlot";
export const metadata: Metadata = { title: 'How Long Does DNS Propagation Take?', description: 'Learn how long DNS propagation usually takes, what affects it, and how to check whether a DNS change has reached different resolvers.' };
export default function Guide(){return <article className="container guide-page"><header className="guide-header"><span className="eyebrow">DNS propagation</span><h1>How Long Does DNS Propagation Take?</h1><p>DNS changes do not move across the internet in one instant. Resolvers cache answers for a period of time, so people in different networks can temporarily receive different results after you change a record or nameserver.</p></header><div className="article-card prose"><h2>What DNS propagation actually means</h2><p>When you update DNS, the authoritative source can change quickly, but recursive resolvers may continue using a previously cached answer until its time to live (TTL) expires. “Propagation” is the period during which those old and new answers coexist.</p><AdSlot slotId="guide-mid-content" className="article-ad-slot" /><h2>How long should it take?</h2><p>Many record changes become visible within minutes or a few hours, but there is no universal completion time. The previous TTL, resolver caching, nameserver changes and provider behaviour all affect what you see. Nameserver changes can also involve registry-level delegation, so treat a fixed “24–48 hour” claim as a rule of thumb rather than a guarantee.</p><h2>How to check progress</h2><p>First confirm that you edited DNS at the provider that is actually authoritative for the domain. Then compare the record from multiple resolvers. If some locations show the new value and others show the old value, caching is a likely explanation.</p><h2>If nothing is changing</h2><p>Check the authoritative nameservers, confirm the hostname and record type, look for conflicting records, and verify that the intended record was saved. If every resolver still returns the old value long after the previous TTL, the change may have been made in the wrong DNS zone.</p><div className="article-cta"><h2>Check your domain</h2><p>Use ZoneCheckr to inspect the live configuration before making changes.</p><Link href="/tools/dns-propagation" className="button button-primary">Check DNS Propagation</Link></div><p className="guide-support">Still stuck? <Link href="/services" className="text-link">Get technical help with your domain →</Link></p></div></article>}
