DNS
Edit DNS records for domains managed by the panel DNS service.
1Overview
DNS lets you manage records for eligible zones attached to your account. It may be unavailable when the domain uses external nameservers or your package disables DNS.
2Before you begin
User-panel actions affect only resources owned by the signed-in hosting account.
3Step-by-step workflow
Open DNS, select the domain, create or update the needed record type, save, and wait for DNS propagation. Use the web-server IP supplied by your hosting account for website A records.
- Open DNS and select the domain whose records you need to change.
- Confirm where its authoritative nameservers are hosted; records here affect public traffic only when this is the active DNS service.
- Read the existing records and identify the exact host name and type.
- Add or edit the requested A, AAAA, CNAME, MX, or TXT record using the value supplied by your service.
- For MX records, enter the mail-server hostname and its priority rather than an IP address.
- Preserve existing verification, SPF, DKIM, and DMARC records unless the change specifically replaces them.
- Save and reopen the zone to verify the value and TTL.
- Allow cached answers to expire and test the affected website or mail service.
4Practical example
Example: to verify a service with a TXT record, enter its provided host label and full verification value. This is separate from changing the website A record.
5Verify the result
Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.
- Reopen the zone and compare the saved value with the requested record.
- Allow DNS propagation and query the authoritative provider if needed.
6Common problems and what to check
Public answers have not changed: confirm the registrar delegation and the record TTL.
Mail fails after an edit: review MX targets and the domain SPF and DKIM records.
A record is refused: check formatting, duplicate names, and whether a CNAME conflicts with another record at the same name.
7Security, impact, and rollback
Do not delete existing MX, SPF, DKIM, DMARC, or verification records unless you know why they exist. DNS changes can take time to reach public resolvers.