Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Edit or Delete Webuzo DNS Records Without Losing Service

Published

Webuzo/BreadbasketDNS

Webuzo DNS Zone Settings can edit or delete records in a managed domain’s zone. Older Bread Basket instructions used Security > DNS Zone Settings; current menu names depend on the installed version. Confirm that this service publishes the domain’s authoritative DNS before changing records.

Preserve the record you intend to change

Keep a private before-state of the exact owner name, type, TTL and value, plus related records needed for recovery. An external authoritative DNS provider needs the change at that provider; editing an inactive local zone is not a synchronization mechanism.

Edit the exact row

  1. Enter the verified HTTPS end-user panel, select the intended domain and open its DNS zone controls.
  2. Locate the exact record and choose its edit action. Check the full effective name rather than relying only on its position in the table.
  3. Enter type-appropriate data: an A record takes IPv4, AAAA takes IPv6, CNAME a hostname and TXT a text value. Do not put a URL or path in an address record.
  4. Set the required TTL in the form’s units and save. TTL is a cache lifetime, not a scheduled date when the authoritative record deletes itself.
  5. Reopen the record and verify the saved name, type and value. Check for unintended duplicate records.

Delete only after checking dependencies

Select the exact row’s delete action, confirm its identity and complete any save/apply confirmation. This removes the authoritative entry once published; it does not erase cached answers immediately. Do not delete a whole domain, primary-domain assignment or unrelated records to repair one entry.

Check whether the record supports mail, certificate validation, service verification or another alias before removing it. CNAME data cannot generally coexist with unrelated record data at the same owner name. Restore the verified previous values if a narrow change needs rollback.

Verify beyond the panel

Query the actual authoritative nameserver for the precise name/type, compare recursive answers and test the affected service. An old recursive answer and an incorrect authoritative answer are different problems. Do not wait a fixed 24 hours before investigating a missing or malformed authoritative record.

References: Webuzo DNS Zone Setting and historical edit workflow.

Reviewed October 15, 2026. Edit/delete tasks were consolidated with the legacy path preserved. No customer zone or panel operation was changed or executed.

Related guides

Account services are unavailable until the production backend is configured.