DNS and nameservers

Nameservers

Read and set from the domain’s Nameservers page in WHMCS, for both you and the customer.

What a new registration gets

In order of precedence:

1. Nameservers submitted with the order — the customer’s own choice, or WHMCS’s system default nameservers if you have those configured.
2. The module’s Default Nameserver 1–4 settings, if the order carried none.
3. Nothing — the domain keeps whatever Porkbun assigns, which is Porkbun’s own nameservers.

The DNS hosting decision

The default nameserver fields ship pre-filled with Porkbun’s nameservers:

curitiba.ns.porkbun.com
fortaleza.ns.porkbun.com
maceio.ns.porkbun.com
salvador.ns.porkbun.com

Left as they are, new domains use Porkbun-hosted DNS, which is free and means the WHMCS DNS tab manages records directly. For most resellers this is what you want: one login for your customer, no separate DNS panel.

Replace all four if you host DNS elsewhere — your own cluster, Cloudflare, a hosting control panel. In that case the WHMCS DNS tab is not where records live, because the domain is not using Porkbun’s DNS, and editing there will have no effect on what resolves.

DNS records

When a domain uses Porkbun nameservers, the WHMCS DNS Management tab reads and writes Porkbun’s host records: A, AAAA, CNAME, MX, TXT, SRV, CAA and the rest.

TTLs are preserved

WHMCS’s DNS tab has no TTL column. Rather than letting every edit reset the TTL to a default, the module reads the record being edited and keeps the TTL it already had at Porkbun.

The same applies to priority on record types WHMCS displays as N/A — the existing value is carried through rather than blanked.

Deletes are off by default

Full DNS sync (allow deletes) is off unless you turn it on.

Off (default): saving DNS from WHMCS adds and updates records, and never deletes. A record created directly in Porkbun that WHMCS does not show survives a save. Safer, and the right choice if anything else also writes to the zone.

On: saving DNS from WHMCS deletes any Porkbun record not present in the WHMCS list. WHMCS becomes the single source of truth for the zone. Choose this only if you are certain nothing else manages those records.

Empty rows

WHMCS sometimes submits blank rows with the DNS form. These are ignored rather than sent to Porkbun as malformed records.

Domain contacts

Registrant, admin, tech and billing contacts are readable and editable from the WHMCS domain page.

Phone numbers have two fields

The contact form shows Phone Country Code — digits only, e.g. 44 — separately from Phone. That is how Porkbun stores and validates them, and it rejects a contact update outright with a valid phoneCountryCode (1-999) is required if the code is missing.

Enter the national number in Phone. If a registry rejects the number itself, try it without the national trunk prefix — 2071234567 rather than 02071234567. Most registries want it that way, though a few, Italy among them, do not.

Changing the registrant

Changing registrant details triggers the usual ICANN verification email to the new registrant. That is registry policy, not a module behaviour, and the change does not complete until it is actioned.

WHOIS privacy

Porkbun provides free WHOIS privacy on TLDs that support it, enabled automatically on new registrations.

There is no API toggle to turn it on or off after the fact, so WHMCS’s ID Protection switch cannot control it. The account-level default can be changed under Account Security Settings at porkbun.com.