Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Add and Edit MX Records in Webuzo

Published

Webuzo/Breadbasket

An MX record names a mail exchanger for a domain and includes a preference number. It controls where senders attempt incoming delivery, not where a mail client submits outgoing messages. Webuzo’s MX controls do not create the destination mailboxes or automatically reconcile an external authoritative DNS provider.

Plan the destination first

Obtain the exact mail-server hostname and priority from the receiving provider. MX data must be a hostname, not an IP address or URL. The target must resolve appropriately and should not be a CNAME alias. Lower preference numbers have higher delivery preference; multiple MX records are not a promise of mailbox synchronization.

Add the record

  1. Use the verified HTTPS Webuzo end-user panel and select the intended domain.
  2. Open the installed MX-record controls under Email. Legacy Bread Basket used Email Server > MX Record; newer DNS interfaces may present the operation in zone management.
  3. Enter the owner/domain, preference and exact destination hostname, checking how the form treats a trailing dot.
  4. Save or choose Add, then inspect the resulting full record. Confirm that the nameservers serving public DNS received it.

Edit an existing MX safely

Record the previous MX set before changing it. Select the exact domain and MX row, use its edit action, update preference/destination and save. Inspect the whole resulting set rather than assuming an unrelated old provider should remain as a backup. Coordinate intentional removal of obsolete MX records with the receiving provider and retain rollback information.

If moving mail externally, review local mail-routing behavior separately. Old mailbox contents do not move with the DNS record, and historical mail may still need preservation. Keep both sides operational during a planned transition where appropriate; do not delete existing mail to force DNS to update.

Verify real receiving service

Check authoritative MX answers, target address records and recursive responses. Then send a harmless authorized external test to a provisioned mailbox and inspect the actual result. A saved row or DNS answer does not establish account existence, filtering acceptance or inbox placement.

References: Webuzo MX creation and DNS zone management.

Reviewed October 15, 2026. The matching edit task was retained in this lifecycle guide. No MX record, mailbox or mail route was changed.

Related guides

Account services are unavailable until the production backend is configured.