Get your domain onto Help4 nameservers.

Pick the registrar, copy the Help4 nameservers, follow the exact control-panel path, and generate a support note if the customer needs their registrar to do it for them.

Important: changing nameservers moves DNS management to Help4. Make sure the Help4 zone already has the site's web, mail, verification, and security records before saving at the registrar.

Help4 nameservers

Use these as custom nameservers at the registrar. Do not enter IP addresses unless Help4 support explicitly asks for glue/private nameserver work.

Operational note: ns1.help4.net through ns6.help4.net are the standard customer-facing names. Older Help4 labels such as ink, doodle, bounce, pixel, sketch, and quil are legacy authority labels and map onto the same GeoDNS fabric.

Registrar steps

Do-not-break checklist

This is the little guardrail box. It keeps DNS cutover from becoming a tiny angry weather system.

Help4 has imported the current zone or rebuilt web, mail, TXT, CAA, DKIM, SPF, DMARC, and verification records.
The registrar account is paid, unlocked enough to edit nameservers, and not in clientHold or serverHold status.
DNSSEC DS records are removed or coordinated with Help4 before nameserver cutover.
Mail provider records are present in Help4 DNS before cutover, especially MX and DKIM.
Someone is ready to test the public site, www, email, and SSL after saving.

Generated registrar support note

If the customer is stuck, paste this into their registrar support chat. It avoids the classic “where do I click?” loop.

Verify after saving

Nameserver check

dig +short NS example.com

You want to see the Help4 nameservers. Some resolvers update quickly; global propagation can take longer.

Website and email check

Load the root domain, www, an upload/media file, and send a small test email. If email fails, compare MX/TXT/DKIM/DMARC against the pre-cutover export.

Registrar source links

Interfaces move around, so these helper steps are backed by current registrar help docs where available.