Most of the time nothing is broken. Your records are right, and the internet’s address book has not caught up with them yet. Both Lovable and Base44 say the wait can run to 72 hours, and both say most domains come through much sooner. The rest of the time one record is wrong, an old record is still in the way, or a setting at your domain company is fighting the builder. The state word the builder shows, plus one check you can run in a browser, tells you which.
What DNS is, and why “pending” usually means waiting
A domain is a name. The computers that serve your app have numeric addresses. DNS, the Domain Name System, is the address book that turns one into the other, and every browser looks a name up in it before it can load anything. When you bought your domain, you bought the name. Connecting it to your app means writing two kinds of entry in that book. One says “this name lives at the builder’s servers”: an A record, which is a name pointing to an address. The other proves you own the name: a TXT record, which is a line of text the builder gave you to paste in. Lovable asks for both. Base44 asks for an A record for the bare domain and a CNAME, which is a name pointing at another name, for the www version.
The catch is that the address book is not one book. It is thousands of copies around the world, each refreshing on its own schedule. Your change goes into the original at the company you bought the domain from, and then it spreads. That spread is what “propagation” means, and it is why the same domain can already work for a friend in another city while your own laptop still gets the old answer. Lovable says most updates are live within a few hours. Base44 says to allow 48 to 72 hours when you added the records yourself, and about 30 minutes when you let it write them for you.
The three states, and what each one means
The first state is pending. Lovable calls it “Verifying” and describes it as “Waiting for DNS records to propagate.” Base44 calls it “Pending verification.” The builder is looking the name up over and over, waiting to see its own address and your ownership text come back. Lovable gives up and shows “Unable to verify” if that takes more than an hour. Base44 leaves the domain pending until you press its Verify button and it finds the records. Pending after an hour means the spread is slow or the record is not what the builder asked for. Pending after three days means the record is wrong.
The second state is connecting. Lovable calls it “Setting up” and says what is happening: “Verification is complete. SSL certificates are being issued.” The certificate is what gives your address the padlock in the browser. Base44 issues it automatically once the domain is verified. This step is entirely on the builder’s side. If Lovable’s version sits in “Stalled,” its docs say to wait up to 72 hours and then contact support. There is nothing at your registrar to fix here.
The third state is the confusing one: the builder says Live, and the browser shows your old website, an error page, or nothing. Lovable’s docs list the causes, and they hold on Base44 too. An old A, AAAA or CNAME record is still in place, so some copies of the address book send visitors to your previous host. Your domain sits behind Cloudflare with the proxy switched on, which both vendors say must be off. Your own browser or network is holding on to the old answer. Or, on Lovable, the app loads but sign-in fails, because your login’s list of allowed return addresses does not include the new domain yet. Base44 adds two more: a domain placed on hold by the registrar, and a CAA record, which is a rule about who may issue certificates for your name.
What is yours to do, and what is only waiting
Yours is the address book entry, and only that. The records at the company where you bought the domain must be exactly the ones the builder lists, and nothing else may point the name elsewhere. Both vendors say to remove any AAAA record, the entry for the newer IPv6 kind of address, which neither uses here. Base44’s docs add that if your domain is with Cloudflare, the records must be set to “DNS only.” Yours is also the plan: on both builders a custom domain needs a paid plan, and no amount of waiting changes that.
Not yours is the spread, and not yours is the certificate. Once the builder reports that it has seen your records, everything after that runs on its side.
The check that tells you which side you are on takes a minute. Open a public DNS lookup site, such as Google’s at dns.google, and type your domain. If the answer is the builder’s address, the address book has updated and the wait is the certificate or your own browser, so open the domain in a private window before you conclude anything. If the answer is your old host’s address, an old record is still in place. If the answer is empty, the record has not spread yet, or was never saved at your registrar.
Why this looks the same on every host
This is not a Lovable or a Base44 problem. Vercel, a hosting company, shows an “Invalid Configuration” alert for the same reasons and says a change of nameservers can take 24 to 48 hours to reach everyone. A domain is a name in a shared book, and every host waits for the same book. Connect one domain by hand and you have done it everywhere.
You can learn more, and get the full prompts and the decision tables, in our course: Lesson 9, It Lives on the Internet. The first lesson is free, no card.
In the next ten minutes: open the builder’s domain page and read the exact state word. Then open dns.google, type your domain, and compare the answer with the address the builder asked for. If they match and the state is still pending or setting up, close the laptop and check tomorrow. If they do not match, the record at your registrar is the whole problem, and it is the one thing here that is yours.