Domain and registrar operations

Use a Porkbun Domain with CMS Max

Keep domain ownership, DNS, email, certificates, redirects, and launch responsibility visible.

Porkbun is a registrar CMS Max teams may use during managed domain work; it is not a native CMS Max application plugin. The right launch method depends on who owns DNS, the required CMS Max records, existing email, subdomains, verification records, and the approved cutover plan.

  • Registrar ownership
  • DNS inventory
  • HTTPS launch
  • Rollback access

Operating model

The domain account is a business-critical control plane.

Avoid single-person ownership, undocumented credentials, unreviewed nameserver changes, and launch plans that ignore email or third-party records.

01

Keep the merchant as owner

Use organization-controlled contact information, billing, renewal, MFA, recovery, and delegated access.

02

Inventory before changing DNS

Record website, email, verification, subdomain, application, TTL, redirect, and security-related records.

03

Choose pointing versus transfer deliberately

A domain can usually point to hosting without moving registrar ownership; use the method approved for the project.

Current CMS Max capability

A managed CMS Max launch coordinates provider and platform responsibilities.

Porkbun controls registrar and optional DNS services; CMS Max supplies the accepted website endpoint, certificates, redirects, and launch requirements.

01 / Capability

Domain registration

Keep registration, renewal, contacts, privacy, transfer lock, and recovery under the approved organization account.

02 / Capability

DNS records

Apply only the CMS Max records and third-party records required for the live architecture.

03 / Capability

Nameserver choice

Decide whether Porkbun or another approved service remains authoritative for DNS.

04 / Capability

Email preservation

Retain MX, SPF, DKIM, DMARC, verification, and related records exactly as required by the mail provider.

05 / Capability

HTTPS and canonical host

Verify root, www, certificates, redirects, preferred hostname, and all HTTP-to-HTTPS behavior.

06 / Capability

Domain forwarding

Use provider forwarding only for the accepted use case and choose temporary or permanent behavior deliberately.

Step-by-step workflow

Prepare the domain before the website cutover window.

Record before-state evidence and lower TTLs only under the approved change plan.

01

Confirm ownership

Verify the registrant, organization access, MFA, renewal, recovery, billing, and authorized contacts.

02

Export DNS

Capture every current record, nameserver, TTL, forwarding rule, subdomain, and dependent service.

03

Receive CMS Max records

Use the exact current endpoint and verification requirements supplied for the tenant.

04

Change and verify

Test root, www, HTTPS, redirects, forms, email, subdomains, analytics, and critical integrations.

05

Monitor and document

Watch DNS propagation and certificates, preserve rollback data, then update ownership and renewal records.

Practical reference

Know which domain action changes which responsibility.

Porkbun documentation distinguishes registrar transfer, DNS pointing, nameserver changes, and URL forwarding.

Registrar transfer
Moves domain registration to another registrar; usually not required to point a site at CMS Max.
DNS pointing
Changes records so the domain resolves to the approved website and services.
Nameserver change
Moves authoritative DNS control and can replace the active record set.
URL forwarding
Provider redirect service for a domain or hostname; select 301 or temporary behavior according to intent.
Transfer lock
Registrar security control that should remain enabled except during an authorized transfer.
CMS Max administration dashboard for a managed website
The website runs on CMS Max while domain registration and DNS remain controlled through the approved provider account.

Current references

Use live product and provider evidence.

Interfaces, policies, plans, services, pricing, and requirements can change. Verify the current CMS Max configuration and official provider sources during implementation.

Porkbun Domain Management FAQ

Resolve the practical questions before launch.

Turn each answer into configuration, representative testing, monitoring, ownership, and a documented recovery path.

Is Porkbun a native CMS Max plugin?

No. Porkbun is a registrar and DNS provider used in some domain workflows; the CMS Max application does not need a Porkbun plugin to serve the website.

Must the domain transfer to CMS Max?

Usually no. The domain can remain with the organization registrar while approved DNS records point to CMS Max.

What is most likely to break during a nameserver change?

Any record not recreated in the new DNS zone, including email, verification, subdomains, third-party applications, and security records.

Does Porkbun support HTTPS forwarding?

Porkbun documents automatic HTTPS for its forwarding service, subject to the current provider configuration and domain requirements.

Who should own the registrar account?

The customer organization should retain durable ownership, renewal, billing, MFA, recovery, and authorized access.

Build for real operations

Launch the domain without losing the services attached to it.

CMS Max can coordinate the website endpoint, redirects, certificates, verification, and cutover checklist with the organization domain owner.

Building Relationships with Web Developers and Marketing Agencies that want better results

The world's fastest and most SEO friendly website code.