How to Point Your Domain to Chapter22 Hosting

Pointing a domain is a DNS change, not a file copy. Get the target IP or nameservers from the Chapter22 client area, then update the registrar or DNS host.

Option A — Use Chapter22 nameservers (recommended when available)

In the client area, open the web hosting service and copy the nameservers.
At your registrar, set custom nameservers to those values.
Wait for registrar delegation to update.
Confirm with:

dig NS yourdomain.com +short
dig A yourdomain.com +short

Option B — Keep DNS where it is (A / CNAME records)

Copy the hosting account IPv4 (and IPv6 if provided).
Create or update:

- @ A → hosting IPv4 - www A or CNAME → @ or the same IP (follow your DNS host’s pattern)

Leave MX alone unless you are also moving email.
Lower TTL to 300 seconds a day before cutover when you can.

Verify before SSL

dig A yourdomain.com @1.1.1.1 +short
dig A www.yourdomain.com @1.1.1.1 +short
curl -I http://yourdomain.com

When the A record returns the Chapter22 IP from a public resolver, continue with Let’s Encrypt SSL.

Email caution

Changing A records does not move mail. If MX still points at the old host, leave it until mailboxes are migrated. Align SPF/DKIM after any mail move.

Rollback

Keep the previous A/NS values documented for 48 hours. Raising TTL again after a successful cutover reduces chatter on busy domains.

Frequently Asked Questions

Should I use nameservers or A records?

Nameservers are simplest when Chapter22 (or cPanel DNS) should manage all records including mail. A/CNAME at your current DNS host is fine if you need to keep DNS elsewhere.

How long does DNS take?

Often minutes when TTL was lowered beforehand; otherwise up to the previous TTL (commonly 1 hour to 48 hours).

My site shows the old host after I changed DNS.

Flush local DNS, try a phone on cellular, and verify the public A record with dig/nslookup against a public resolver.

Need help?

If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.

Build the server. Grow the community. Start your next chapter.