What Is DNS? A Plain-English Explanation for Builders

AI Build South Africa

A fundamentals guide, written for someone pointing a .co.za domain at an AI-built app, not someone administering DNS professionally.

Quick answer

DNS is the system that turns a domain name, the words you type into a browser, into the real, numeric address a computer actually needs to connect to your site. Without it, you'd have to remember a string of numbers instead of a name. Pointing your own domain at an AI-built app means adding specific DNS records at your registrar: which type you need depends on whether you're pointing your root domain (yourbusiness.co.za) or a subdomain (www.yourbusiness.co.za), a distinction that trips up more real setups than anything else about DNS.

Tools for this build

Custom Prompt Builder

Turns your task, in your own words, into a prompt with clear limits for your AI coding agent.

POPIA Compliance Checker

Worth running once your own domain is live and handling real visitor data.

PayFast Webhook Generator

A webhook needs a real, reachable domain, exactly what DNS provides.

The one-sentence version: the internet's phonebook

Every website is really reachable at a numeric IP address, not a name. DNS exists so nobody has to remember those numbers: you type a domain name, and somewhere in the background a DNS lookup translates it into the actual address your browser connects to. That translation is stored as a set of records at your domain's registrar, each one telling DNS what a specific name should resolve to, and getting these right is the entire job whenever you're connecting your own domain to an AI-built app.

What you type vs. what actually connects

A domain name

What a visitor types or clicks:

Human-readable, easy to remember, means nothing to a computer directly

A DNS record

What actually resolves it:

Points the name at a real address or another name, set at your registrar

AI Build · aibuild.co.za

The record types you'll actually touch: A, CNAME, ANAME/ALIAS, AAAA

A handful of record types cover almost every real setup connecting a domain to an AI builder. An A record points a domain straight at a numeric IPv4 address. A CNAME record points a domain at another domain name instead of a raw address, more flexible if the target ever changes, but it can't legally sit on a root domain alongside the other records that domain needs. An ANAME or ALIAS record is the usual fix for that: it behaves like a CNAME but is allowed at the root, since it isn't an official DNS standard type at all, individual DNS providers implement it themselves behind the scenes. An AAAA record is the IPv6 equivalent of an A record, and worth actively checking for and deleting on a domain you're pointing at a platform that doesn't expect one, since a leftover AAAA record can silently block the whole connection.

Why your root domain can't just use a CNAME

This rule catches out a lot of people connecting a domain for the first time. The DNS specification doesn't allow a CNAME record to coexist with other records a root domain needs, most importantly MX records for email, so a plain CNAME on yourbusiness.co.za simply isn't valid, even though it's exactly what you'd reach for on a subdomain like www. Our guide to connecting your own domain to an AI-built site covers what to put there instead (an A record, or an ANAME/ALIAS record, whichever your builder asks for) and which old records to delete first.

Why DNS changes take hours, not seconds: propagation

A DNS record you just changed doesn't take effect everywhere instantly. Every DNS server that might be asked about your domain caches its last answer for a set period before checking again, which is what makes DNS fast for everyone else's ordinary browsing but slow for you the moment you change something. Propagation is the name for this delay, and it can take anywhere from a few minutes to around 24 to 48 hours depending on your specific domain's caching settings and registrar. Our guide to connecting your own domain explains how to shorten the wait and what to check if it runs longer than your builder says.

Not every DNS setup needs all of this

If you're using your AI builder's own subdomain, something like yourapp.lovable.app, none of this applies: it's already fully working the moment your builder deploys it, no DNS configuration required from you at all. DNS only becomes something you actively touch once you want your own domain pointing at that same deployment instead, which is a real, worthwhile step for a live business but genuinely optional for testing or a first build.

Where to go next

Putting these records to work on your own .co.za or other domain: How to Connect Your Domain to Your AI-Built Website.
Turning a builder's preview into a live, reachable site in the first place: What Does Deployment Actually Mean?.

Not affiliated with the platforms we write about

AI Build South Africa is an independent resource. We're not endorsed by, or an official partner of, PayFast, Yoco, Peach Payments, Ozow, Meta, Lovable, Base44, Bolt.new or Anthropic. We do participate in affiliate and referral programmes with some of these providers, including Base44. See our Disclaimer for the full disclosure and our Terms of Service for the wider terms.

Frequently asked questions

Why can't I use a CNAME record on my root domain?

DNS rules don't allow a CNAME to coexist with the other record types a root domain needs, like MX records for email. An ANAME or ALIAS record is the usual fix: it behaves like a CNAME but is legal at the root, since it isn't an official DNS standard type, individual DNS providers implement it themselves. If your registrar's panel doesn't offer ANAME or ALIAS, an A record pointed at the platform's IP address is the fallback where your builder accepts one; if it doesn't, point your nameservers at the builder instead.

What's the difference between an A record and a CNAME record?

An A record points a domain straight at a numeric IP address. A CNAME record points a domain at another domain name instead, which then gets resolved to an IP address in turn. A CNAME is more flexible if the target's IP address ever changes, since you never have to update it yourself, but it can't legally be used on a root domain.

What is propagation, and why does it take so long?

Propagation is the time it takes for a DNS change to reach every server around the world that might be asked about your domain, since each one caches an answer for a set period rather than checking fresh every time. It's not instant by design, and can take anywhere from minutes to around 24 to 48 hours depending on your domain's specific caching settings and your registrar.

What is a TXT record for?

A TXT record holds arbitrary text attached to your domain, most commonly used to prove you own it (a verification code from Google Search Console or a platform like Base44) or to set email authentication rules like SPF, which help stop other people's emails from being sent pretending to come from your domain.

Do I need to touch DNS at all if I'm using my AI builder's own subdomain?

No. A subdomain like yourapp.lovable.app is already fully working the moment your builder deploys it, no DNS configuration required on your part. DNS only becomes something you touch once you want your own domain, a .co.za address, pointing at that same deployment instead.

Why would deleting a record fix a connection that isn't working?

A leftover record from a previous host, most often an old A or AAAA record nobody removed, can conflict with the new one you've just added, and DNS resolvers can pick either one inconsistently. This is one of the more common, least obvious causes of a domain connection that half-works or fails intermittently: checking for and deleting stale records is worth doing before assuming the new configuration itself is wrong.