Change nameservers for a domain bought through Lovable

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Change nameservers for a domain bought through Lovable working in a real project rather than a sandbox.

   Set up Change nameservers for a domain bought through Lovable in this project — gain more control over your custom domains' DNS. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Point a Lovable-purchased domain at a custom DNS provider

   The record lists this as one of the jobs Change nameservers for a domain bought through Lovable is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Change nameservers for a domain bought through Lovable for point a Lovable-purchased domain at a custom DNS provider. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Change nameservers for a domain bought through Lovable is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Change nameservers for a domain bought through Lovable before I publish. Check manage nameserver settings and switch to custom DNS providers, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Recover from a DNS misconfiguration without losing the domain

   A second job the record lists for Change nameservers for a domain bought through Lovable, useful once the first path works.

   Extend this project so Change nameservers for a domain bought through Lovable also covers recover from a DNS misconfiguration without losing the domain. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Change nameservers for a domain bought through Lovable?

  Change nameservers for a domain bought through Lovable is Lovable's Cloud feature: Gain more control over your custom domains' DNS. Workspace admins can now point domains purchased through Lovable to their own custom nameservers, enhancing flexibility and control over DNS management while using Lovable's infrastructure for domains.

• Is Change nameservers for a domain bought through Lovable GA or in beta?

  Change nameservers for a domain bought through Lovable is generally available (GA) on Lovable.

• What Lovable plan includes Change nameservers for a domain bought through Lovable?

  Change nameservers for a domain bought through Lovable is available on all Lovable plans.

• When did Change nameservers for a domain bought through Lovable launch?

  Change nameservers for a domain bought through Lovable launched on Jun 18, 2026.

• One credit balance and clearer usage insightsSame category, also GA · Jun 2026
• Publish and install private npm packagesSame category, also GA · Jun 2026
• Improve Database Performance DetectionSame category · Jun 2026