Nameservers vs. DNS records: the two-step handoff everyone confuses

A domain's nameservers (set at the registrar, lesson 1's own territory) determine which DNS provider's servers the rest of the internet asks when resolving that domain at all — Networking Fundamentals' own DNS lesson covered this exact resolution chain. The records (A, CNAME, MX, TXT) are configured with whichever provider the nameservers point at, and they're what actually answers "what's the IP," "where's the mail server," and so on.

A genuinely common mistake: adding or changing an A record at the registrar's own DNS panel, while the domain's nameservers actually point somewhere else entirely (Cloudflare, say) — the change has zero effect, because nothing on the internet is actually asking the registrar's DNS panel anything; every resolver is asking Cloudflare instead, which never saw the change at all. "I updated my DNS but nothing happened" is, after ruling out simple propagation delay (Networking Fundamentals' own TTL lesson), very often exactly this: editing records at the wrong place relative to where the nameservers actually delegate authority.

This is exactly the pattern AWS's own Route 53 lesson described in one line: creating a hosted zone in Route 53 does nothing for real traffic until the domain's nameservers, at whatever registrar it was purchased through, are updated to point at Route 53's own assigned nameservers — the registration and the DNS authority are two genuinely separate relationships, and changing one doesn't automatically change the other.

A registrar's own DNS panel is often basic — no advanced record types, no analytics, no fast propagation guarantees. Pointing nameservers at a dedicated DNS provider (Cloudflare being the most common free choice) gets access to that provider's own feature set — often faster propagation, DNSSEC support, more sophisticated routing options — while the domain itself stays registered wherever it was originally purchased. This split (registrar ≠ DNS provider) is completely normal and, for anyone doing anything beyond the simplest setup, usually the better default.