An A record maps a hostname to an IPv4 address. Edit it in cPanel only when the domain’s authoritative DNS is actually served by this hosting DNS system; otherwise make the record at the active DNS provider.
IN THIS ARTICLE
Check access and requirements
Obtain the correct destination IP from the service you are connecting. Record the existing value and TTL, and check whether the hostname already has a CNAME or an AAAA record that affects how visitors connect.
01 Add an IPv4 A record in cPanel Zone Editor
- Open Zone Editor, find the domain and choose Manage or its A Record shortcut.
- Add an A record for the exact hostname, such as
app.example.com. Review the completed name to avoid accidentally appending the domain twice. - Enter the supplied IPv4 address. The documentation address
192.0.2.10is an example, not a real hosting destination. - Save the record and inspect the final name, type, TTL and address in the zone list.
- Query the authoritative DNS and then a public resolver. Allow previously cached answers to expire according to their existing TTL before concluding the change failed.
02 Example: map an A record to the Zone Editor fields
Suppose the destination service assigns an IPv4 address to app.example.com. In cPanel Zone Editor, select the domain and add one A record using the actual assigned address. The documentation address below is not a Nabtech hosting address.
Name: app.example.com.
Type: A
TTL: 300
Address: 192.0.2.10
Verification:
dig app.example.com A +noall +answer
Read the result: The final name in the saved zone must be app.example.com, without example.com appended twice. The answer should contain the intended IPv4 value once cached older responses expire. An existing CNAME at that exact name conflicts with an ordinary A record and needs a reviewed decision.
Check any AAAA record and verify that the destination web server recognises app.example.com. DNS does not create a site directory or install a certificate. If cPanel is not authoritative for this domain, make the public record at the actual DNS provider instead.
Confirm the expected result
The hostname should resolve to the intended address. Test the actual website and HTTPS separately because correct DNS does not create hosting configuration or a certificate.
Why does the domain still open the old site after an A-record change?
If the old site remains, verify authoritative nameservers and any competing AAAA record. Do not add several conflicting A records unless the service explicitly supports that design. If the wrong address was entered, restore the recorded value and account for cached responses.