Manage Bought-Domain DNS and Nameservers
Add, edit, or delete seven DNS record types, resolve conflicts, and change nameserver delegation for a domain bought with BillionBiz.
Change the records for a bought domain, or move its DNS delegation to your chosen provider. Review the existing store and email records before changing either.
Availability
Manage domain appears on each bought domain in My domains, but the registrar-management features work only when they are enabled for your store. If they are switched off, changes are refused with Domain registration management is currently unavailable. Until then your store keeps working on its current address.
Screen: Online Store → Domains → My domains → Manage domain → DNS records (under storefront → Domains in the new admin sidebar). Choose Scope → Store if shown. Sign in as the store owner. Support/impersonation sessions are read-only; Refresh details and Back to my domains let you inspect or leave the details without making a change.
Read the complete DNS zone
The table has the columns Type, Host, Value, TTL, and Actions. Add record opens a new record form. An empty editable zone says the first write activates registrar DNS; it does not prove another DNS provider has no records.
How each row reads:
- Long values. A value that does not fit its cell is cut off with a chevron. Click the value (its label is Show full host and value) to open a detail row with the complete Host and Value; click again (Hide record details) to collapse it.
- Copy value. The copy icon beside each value copies it and briefly changes to Copied. If the browser blocks copying, you see Could not copy. Try again or select the value to copy it.; select the text from the expanded detail row instead.
- MX and SRV extras. An MX or SRV row shows its Priority under the value. An SRV row's Weight and Port are listed, greyed out and read-only, at the top of its More actions menu.
- Used by your store. An A or CNAME record that connects your store to this domain carries a green Used by your store tag.
- Filter and search. Once the zone has more than six records, a row of type chips (All plus one chip per type present; the group is labelled Filter records by type) and a Search host or value box appear. If nothing matches, the table says No records match these filters.
Each row has an Edit button and a More actions menu (the three-dot button). The menu holds Delete record.
The page notes that changes can take up to 24 to 48 hours to show everywhere.
Editing requires confirmed registrar-managed nameservers, a fresh readable zone, and a known registrar minimum TTL. Loading, a failed read, external/unconfirmed delegation, a pending change, or a record-version conflict can disable the controls. Disputed, restricted, or read-only registrations cannot be changed. Use Reload records when offered after a zone error or conflict.
Quick setup: email and verification records
Above the table, Quick setup adds a standard group of records in one go. Choose Google Workspace, Zoho Mail India, or Microsoft 365 for email, or the Verify domain ownership link (hint: Add a verification TXT record) for a site-verification TXT record.
Open the preset and supply any value
Google Workspace needs no input; it uses the standard MX and SPF records. The others ask for one value from your provider: SPF TXT value from your Zoho Admin Console, MX target from Microsoft 365 Admin Center, or Complete TXT value from Google Search Console, Meta or your provider for ownership checks. Copy these from your provider; BillionBiz cannot know them.
Click Review records
The dialog lists Records to configure. If the setup would overwrite existing records, a second list headed Will be removed shows each as type, host and value. A value that does not fit (for example, a second SPF record or a conflicting alias) is rejected with a message asking you to resolve the existing records first. If everything is already present it says These records are already configured. and Apply records stays disabled.
Acknowledge and apply
When Will be removed is shown, tick I understand these changes replace my existing records and may affect email or my store connection.; Apply records is disabled until you do. Click Apply records (it reads Applying records… while running). On success the page says Records configured. If setup stops partway, retry: completed steps are not repeated.
The preset buttons are disabled in the same situations as Add record (see the troubleshooting section below).
Add a record
Choose Type and Host
Click Add record, then choose Type. In Host, use @ for the domain apex, www for that subdomain, or another relative host within your domain. Do not enter a URL or a hostname belonging to a different domain. A wildcard is allowed only in the leftmost label; service underscores are accepted for TXT or SRV hosts.
Enter Value and applicable numeric fields
Use the type table below. Priority appears for MX and SRV; Weight and Port appear only for SRV. Each is a whole number from 0 to 65535. Do not supply numeric fields that do not apply to the selected type.
Set TTL and save
In TTL (seconds), enter a whole number at or above the displayed minimum, up to 2147483647. The minimum comes from the registrar; do not assume every domain uses the same minimum. Click Save. Cancel closes the form without submitting.
Confirm any service impact
For apex, www, nameserver, or store-connection record changes, a warning can require I understand and want to continue. and Confirm change. Confirmation remains disabled until acknowledged. Wait for the confirmed outcome and reload the records before assuming the change took effect.
| Type | Value and additional requirements |
|---|---|
| A | A valid IPv4 address, such as 203.0.113.10, without a port or CIDR suffix |
| AAAA | A valid IPv6 address, without a port, CIDR suffix, or zone suffix |
| CNAME | A hostname, not an IP or URL. Cannot be at @, coexist with other records at the same host, point to itself, or create an alias cycle |
| MX | A mail-server hostname and Priority |
| TXT | Decoded text, up to 2048 UTF-8 bytes, without control characters or incomplete quotation marks. Long values require registrar support for legal TXT chunks |
| NS | A nameserver hostname. Zone NS records are separate from the registration's Nameservers delegation setting |
| SRV | A target hostname plus Priority, Weight, and Port. The host must begin with _service._tcp or _service._udp |
The form also shows help text under its fields. Under Host: Use @ for the apex or a host relative to this domain. Under TTL (seconds): Minimum: N seconds., where N is the zone's minimum. Under Type the help depends on the choice: A reads An IPv4 address, such as 203.0.113.10.; AAAA An IPv6 address, such as 2001:db8::1.; CNAME A hostname alias. Enter the destination hostname without https://.; MX Your mail server hostname; lower priority numbers are preferred.; TXT Paste the exact text supplied by your verification or email provider.; NS An authoritative nameserver hostname. Changing this can disconnect your store.; SRV A service target hostname; include priority, weight and port.
A zone with no records yet shows No editable records yet. The first write activates the registrar DNS zone. below the table header, with no record rows; adding the first record creates the zone. If a search or filter hides every record, the list shows a no-match message instead of this one.
Edit or delete an existing record
Click Edit on a row to open Edit record with its current values. Type and Host are locked while editing; you can change Value, TTL (seconds), and the numeric fields applicable to that type. To change the host or type, review the impact of deleting and adding records instead. Click Save and acknowledge any warning, or Cancel to leave it.
To delete, open More actions on the row and choose Delete record. The Confirm DNS change dialog opens; read it, select I understand and want to continue., then Confirm change; Cancel leaves the record. Deleting a record used by another service, such as email, can affect that service. The store connection is checked again after the registrar confirms the change.
Records used by your store show a Used by your store tag. The tag is informational and does not block Delete record. Choosing it opens the Confirm DNS change dialog described above, which reads This change can disconnect your store or other services. The connection will be checked again after the registrar confirms the change. with the acknowledgement checkbox. Delete record is greyed out only while the DNS tab is locked: read-only access, records still loading or failed to load, a read-only or stale zone, nameservers not managed by BillionBiz, the zone's minimum TTL unavailable, an edit conflict, or another change in progress. Deleting a record your store depends on can take the store offline; to stop serving the store deliberately, disconnect the domain from your store instead; see Store connection. You can also edit such a record (the edit asks you to acknowledge the warning).
A response that says the outcome is being checked means confirmation is pending. Do not repeat the write. If the record changed elsewhere, Reload records closes the stale form and loads the latest version; review that version before editing again. Reloading does not apply your unsaved edits.
Change nameserver delegation
Screen: Online Store → Domains → My domains → Manage domain → Nameservers. The screen displays the confirmed nameservers and whether DNS is registrar-managed, managed elsewhere, or unconfirmed.
Prepare the destination zone first
Changing delegation can disconnect your store, email, and third-party services. Registrar DNS records do not take effect while external nameservers are in use, and the BillionBiz DNS editor is read-only then.
Enter Custom nameservers
Enter 2–13 distinct nameserver hostnames, one per line; comma-separated entries are also accepted. Use hostnames rather than IPs or URLs. Prepare the corresponding destination DNS records before changing delegation.
Save and acknowledge the change
Click Save custom nameservers. Invalid or duplicate entries show a validation message. Read Change nameserver delegation?, select I understand and want to continue., and click Confirm change. Cancel closes the dialog without submitting.
Check confirmation and service reachability
Refresh the details and inspect the confirmed nameserver list. A pending request is not confirmation that delegation changed. Check your store and other services using the destination DNS before sharing the address.
Restore managed nameservers is offered when delegation is external or unconfirmed and is disabled if it is already confirmed managed. It uses the reconnect flow to restore registrar-managed delegation and the store connection records. Read the restoration warning, acknowledge it, and Confirm change; records at the former provider stop being used. Recheck Store connection and HTTPS afterwards.
Troubleshooting: why don't I see X?
Why can't I add, edit, or delete records?
The rollout and owner session are required. External nameservers, a failed registrar read (the Registrar details are unavailable banner), a missing minimum TTL, loading/errors, or a pending/conflicting operation disable editing. Confirm delegation in Nameservers, then refresh. Support and impersonation sessions cannot write.
Why can't I delete this record?
Check the More actions menu on that row. If Delete record is greyed out with Used by your store. Remove it by disconnecting the domain., the record is what points customers at your store, and deleting it directly is blocked so you cannot take the store offline by accident. Disconnect the domain from your store first. If every delete and edit is disabled, not just this one, the zone is locked; see the previous question.
Why is Save rejected for a CNAME or target?
CNAME cannot use the apex, share its host with another record, or form an alias cycle. CNAME, MX, NS, and SRV values must be hostnames without URL syntax or IP addresses. Reload the complete zone to find conflicts rather than checking only the visible record you were editing.
Why does the form say the record changed elsewhere?
The saved record version is stale. Use Reload records, read the new values, and start a new edit. The form deliberately blocks overwriting someone else's newer change.
Why did changing DNS not fix my store?
External delegation ignores registrar DNS. With managed delegation, a confirmed record write still requires the store connection and HTTPS checks to succeed. Inspect Overview → Store connection and use the reconnect guide after reviewing conflicts. A DNS activation failure means no record change was confirmed; refresh before retrying.