Do I need to understand DNS to launch my first app?

Not if you use your host's free subdomain. If you add a custom domain, you only need to copy the records your host provides — no deep expertise required.

How long does DNS propagation take?

Often 15 minutes to a few hours. In rare cases up to 48 hours. TTL and geographic caching affect timing.

What is the difference between DNS and a domain?

The domain is the name you rent (yourapp.com). DNS is the system and records that tell browsers where that name points.

Why does my site work on vercel.app but not on my custom domain?

The app is fine — DNS is misconfigured or still propagating. Verify records match your host's instructions exactly.

Can I test DNS before switching production traffic?

Yes. Some makers use a subdomain like staging.yourapp.com first, or check records with online DNS lookup tools before sharing the main domain.

Glossary

What Is DNS?

DNS (Domain Name System) is how the internet turns yourapp.com into the server address where your app actually lives. You do not need to become a DNS expert to launch — but knowing the basics prevents the frustrating 'my domain does not work' phase every maker hits eventually.

Updated July 2026 · 6 min read

Written for AI makers using tools like Cursor, Bolt, Lovable, Replit, Claude, and ChatGPT.

Quick answer

DNS is the internet's phone book: it maps human-readable domain names to IP addresses or hostnames so browsers know where to send requests. When you connect a custom domain, you add DNS records at your registrar that point to your hosting provider.

Who this is for

Your host says 'add these DNS records' and the jargon feels opaque
You connected a domain but the site still does not load after an hour
You want to understand A records, CNAME records, and TXT records without a networking course

A simple definition

Every device on the internet has an address — an IP address like 192.0.2.1. Remembering IPs for every website is impossible, so DNS gives us names instead. When you visit makerlaunch.com, your browser asks a DNS server: 'What address is makerlaunch.com?' The answer comes back in milliseconds, and your browser connects to that server.

DNS is distributed — thousands of servers worldwide cache answers so lookups stay fast. That caching is why changes are not instant: when you update a record, old answers may linger until they expire (TTL — time to live).

For launching an app, you mostly interact with DNS at your domain registrar (Namecheap, Cloudflare, etc.) or a DNS provider. Your hosting platform tells you which records to create; you paste them in and wait.

Why it matters at launch

If you launch only on your host's free subdomain (yourapp.vercel.app), DNS is handled for you. You never touch a DNS panel. That is the recommended first-launch path.

DNS enters the picture when you connect a custom domain. A wrong record — mistyped CNAME, missing A record, conflicting old records — means your domain points nowhere or points at the wrong server. Your app may work perfectly on the default URL while yourapp.com shows errors.

Some launch steps depend on DNS beyond websites: email verification (TXT records), OAuth redirect URLs, and SSL certificate issuance. Hosting platforms like Vercel verify domain ownership through DNS before issuing HTTPS certificates.

Understanding DNS at a beginner level saves hours of guessing. Copy records from your host, do not invent values, and wait for propagation before declaring failure.

A beginner example

You deployed a Next.js app to Vercel at mystartup.vercel.app. Everything works. You bought mystartup.com and opened Vercel → Settings → Domains → Add.

Vercel displays: for www.mystartup.com, create a CNAME pointing to cname.vercel-dns.com. For the root domain mystartup.com, add an A record to 76.76.21.21 (example IP — always use your host's current values).

You log into Cloudflare, open DNS for mystartup.com, and add those two records. You remove any old parking-page records the registrar created by default. Within 30 minutes, www.mystartup.com loads your app. The root domain may take longer.

You test in an incognito window to avoid browser cache. Both mystartup.vercel.app and mystartup.com show the same site. Launch success — DNS did its job.

Common DNS record types

You will see a handful of record types in host instructions. These four cover most launch scenarios:

A record — points a domain directly to an IPv4 address (common for root domains on some hosts)
AAAA record — same as A but for IPv6 addresses
CNAME — points a hostname to another hostname (common for www subdomains pointing at Vercel or Netlify)
TXT — text records used for domain verification, SPF email auth, and some SSL workflows

Propagation and TTL

When you save a DNS change, it does not update everywhere instantly. Resolvers worldwide cache old answers until TTL expires — often 300 seconds (5 minutes) to several hours, sometimes longer if TTL was set high previously.

If your domain fails right after adding records, wait. Use dnschecker.org or your host's domain status page to see if records have spread. Changing records repeatedly resets the wait.

Lower TTL before a planned migration if your registrar allows it — advanced tip for later. First-time launchers should focus on correctness over speed.

Registrar DNS vs host-managed DNS

Most beginners keep DNS at the registrar and add records there. Some teams move nameservers to Cloudflare for caching and security, or let Vercel manage DNS entirely.

Only one place should be authoritative. If Vercel manages your DNS, add records in Vercel — not at the registrar. Mixing panels causes conflicts where half the internet sees old data.

When in doubt, follow the single source of truth your hosting platform's domain setup wizard recommends.

Common mistakes

Typo in a CNAME or A record value
How to fix it: Copy-paste from your host's dashboard. Do not retype long hostnames from memory. One wrong character breaks the chain.
Leaving default parking-page records in place
How to fix it: Delete or replace registrar placeholder A records that point at a 'coming soon' page. Conflicting records confuse browsers.
Expecting instant global updates
How to fix it: Wait up to 48 hours for full propagation. Test with your host's default URL meanwhile. Use DNS lookup tools to verify records are live.
CNAME on the root domain where not supported
How to fix it: Some registrars forbid CNAME at the root (@). Use your host's recommended A/AAAA records or ALIAS/ANAME if offered.
Editing DNS at two providers simultaneously
How to fix it: Pick one DNS authority — registrar or host. Point nameservers once and manage all records in that single panel.

Frequently asked questions

Do I need to understand DNS to launch my first app?: Not if you use your host's free subdomain. If you add a custom domain, you only need to copy the records your host provides — no deep expertise required.
How long does DNS propagation take?: Often 15 minutes to a few hours. In rare cases up to 48 hours. TTL and geographic caching affect timing.
What is the difference between DNS and a domain?: The domain is the name you rent (yourapp.com). DNS is the system and records that tell browsers where that name points.
Why does my site work on vercel.app but not on my custom domain?: The app is fine — DNS is misconfigured or still propagating. Verify records match your host's instructions exactly.
Can I test DNS before switching production traffic?: Yes. Some makers use a subdomain like staging.yourapp.com first, or check records with online DNS lookup tools before sharing the main domain.