Connect a GoDaddy domain to LogicWeb nameservers

To connect a GoDaddy domain to LogicWeb, replace the nameservers at GoDaddy with ns1.logicweb.com and ns2.logicweb.com. You keep paying GoDaddy for the registration while our nameservers answer DNS for the site. Make this change after you have previewed a migrated site, not as the first step of a migration.

Preview the site before you change nameservers

If we already copied your cPanel account, the site should respond on the new server IP. Add that IP to your hosts file and browse the site carefully. Our guide on a hosts file that does not fight you walks through that check. Change nameservers only after the preview looks correct.

If the GoDaddy domain and the hosting account are both brand new, you can skip the hosts file step. Point the nameservers, wait for DNS to settle, then let AutoSSL issue the certificate on cPanel.

Change nameservers in your GoDaddy account

1. Sign in at GoDaddy, open Domain Portfolio, select the domain, and open DNS.
2. Choose Nameservers, then Change nameservers, then the option to use your own nameservers.
3. Enter ns1.logicweb.com and ns2.logicweb.com, then save the change.

ns1.logicweb.com
ns2.logicweb.com

GoDaddy may warn that email could break. That only happens if mail still depended on GoDaddy DNS and you did not copy the MX records into our zone first. If mail already runs on Google or Microsoft, place those same MX records in the LogicWeb zone before you switch nameservers.

Confirm DNS now points at LogicWeb

dig NS example.com +short
dig A example.com +short

The NS answers should be the two LogicWeb nameservers. The A record should match the IP on your cPanel account, not a GoDaddy parking address. If nameservers moved but the A record still shows a GoDaddy IP, our zone is missing the record, so add the A record or restore the zone we created at signup.

You can leave the GoDaddy domain registered there and still use LogicWeb hosting. A registrar transfer is a separate request after the site already runs here. If you plan to put Cloudflare in front instead of using our nameservers directly, see Cloudflare in front.