Hosting, domains, and DNS for New Zealand businesses: staying in control of your web presence

Your domain and hosting are foundational infrastructure. They are less visible than design or marketing, but when they go wrong, everything else stops: email bounces, the site disappears, or a migration turns into a multi-day crisis.

This guide explains the moving parts in plain language, highlights NZ-relevant trade-offs, and gives you a practical decision framework.

1. The four assets you should be able to point to

Healthy setups separate concerns so you can recover if one vendor disappoints:

1. Domain registration — Who you pay to keep yourname.co.nz renewed and which registrar holds the authoritative DNS (sometimes split).
2. DNS hosting — Where records live (A, AAAA, CNAME, MX, TXT) that tell the internet where your site and mail go.
3. Web hosting — The server or platform that serves your website files and database.
4. Email hosting — Where mailboxes live (often not the same place as the website, even if a bundle advertises both).

If all four are murky, you do not truly control your presence—you are hoping a single login never breaks.

2. Choosing web hosting: what NZ SMEs actually need

Match hosting to site type and risk tolerance, not to marketing superlatives.

• Simple brochure or portfolio sites — Managed shared or modest VPS-style hosting is often enough if backups, SSL, and support are credible.
• WordPress with plugins and forms — Prefer hosts that understand PHP versions, caching limits, and restore procedures; “unlimited everything” rarely survives reality.
• WooCommerce or busy booking flows — Plan for more CPU/RAM, staging, and monitoring; shared hosting can work early but may pinch at peak.
• Custom apps or high compliance — You may need explicit SLAs, NZ or AU region options, and documented security practices.

Ask providers direct questions: backup frequency and restore process, whether you get SSH/sFTP, how staging works, typical support hours in NZ time, and what happens if the site is compromised.

3. HTTPS (SSL/TLS) without mystique

HTTPS encrypts traffic between visitors and your server. Modern browsers mark HTTP sites as “not secure,” and search engines treat HTTPS as baseline.

Most reputable hosts offer free automated certificates (e.g. Let’s Encrypt). You still need to fix mixed content (HTTP assets on HTTPS pages) and renew monitoring—automation usually handles renewals, but misconfiguration breaks them.

4. DNS: the switchboard everyone ignores until launch week

DNS translates human-readable names into addresses. For SMEs, the critical record types are:

• A / AAAA — Where the website’s hostname points.
• MX — Where email for your domain should be delivered.
• TXT — SPF, DKIM, DMARC for mail authenticity; domain verification for Google, Microsoft, SaaS tools.
• CNAME — Aliases (e.g. www) to another hostname.

Lowering TTL before a migration gives you faster rollback if something misbehaves—plan cutovers when you can watch dashboards, not Friday at 5pm.

Changing nameservers moves all DNS control—double-check MX and TXT so you do not silently break email.

5. Business email: bundled hosting vs Microsoft 365 vs Google Workspace

Many NZ businesses outgrow “free mailboxes with hosting” because of spam reputation, calendar integration, and mobile reliability.

• Bundled/cPanel mail — Can be fine for tiny teams; watch storage, outbound limits, and backup of mail data.
• Microsoft 365 — Strong fit if you live in Outlook, need SharePoint/Teams, or integrate with Windows-centric tools.
• Google Workspace — Strong fit if you prefer Gmail, Meet, and collaborative Docs.

Whichever you pick, implement SPF, DKIM, and DMARC thoughtfully—bad mail authentication hurts deliverability more than most owners realise.

6. Backups and restores: judge by restore, not slogans

A backup you have never restored is a wish. Confirm:

• Frequency (daily for active sites is common).
• Retention (how far back can you go?).
• Whether backups are off-site from the live server.
• How long a restore takes and whether you can self-service a partial file restore.

For WordPress, understand whether backups include both files and database, and test a staging restore after major changes.

7. Domains: renewals, locks, and transfers

Turn on registrar lock to reduce hijack risk. Keep billing contacts current. For .nz domains, understand your registrar’s transfer policy and auth codes.

Letting a domain lapse can mean email and the website stop together—set calendar reminders independent of “we emailed you” notices that land in spam.

8. Migrations: sequence matters

A typical safe order:

1. Clone/site copy to new hosting; test on hosts file or temporary URL.
2. Fix HTTPS, forms, and hard-coded URLs.
3. Lower DNS TTL; plan MX if mail moves.
4. Cut over DNS or repoint A records; monitor logs.
5. Keep old hosting read-only briefly as rollback.

Preserve URL structures or implement 301 redirects—your SEO and bookmarks depend on it.

9. CDN and “speed add-ons”

A CDN caches static assets closer to visitors. For NZ audiences plus international tourists or B2B readers, selective CDN use can help—but misconfiguration also caches HTML you did not mean to cache. Start with clear goals and measure.

10. Frequently asked questions