The Domain Name System (DNS) is a critical component of the internet, responsible for translating human-readable domain names into IP addresses that computers use to identify each other on the network. Managing DNS records is an essential skill for anyone running a website, as it allows you to control how your domain directs traffic to your hosting server. In this guide, you will learn how to manage DNS records in cPanel, specifically using the Zone Editor, to ensure your domain functions correctly.
In this guide
Access the Zone Editor
To manage DNS records in cPanel, you will use the Zone Editor. Start by logging into your cPanel account through the server hostname provided in your welcome email, using port 2083. Once logged in, locate the 'Domains' section on the cPanel dashboard. Click on 'Zone Editor' to access the interface where you can manage DNS records for your domains.
In the Zone Editor, you will see a list of your domains. Next to each domain, you will find options to manage 'A', 'CNAME', and 'MX' records. You can also add new records or edit existing ones. This interface provides a straightforward way to control how your domain name resolves to various services, such as web servers and email servers.
Record types explained
A Record
An A (Address) record maps a domain to an IPv4 address. For example, if your server's IP address is 192.0.2.1, you would create an A record pointing 'yourdomain.co.za' to this IP.
AAAA Record
Similar to an A record, an AAAA record maps a domain to an IPv6 address. Use this when your server supports IPv6, such as 2001:0db8:85a3:0000:0000:8a2e:0370:7334.
CNAME Record
A CNAME (Canonical Name) record is used to alias one domain name to another. For example, if you want 'www.yourdomain.co.za' to point to 'yourdomain.co.za', you would use a CNAME record.
MX Record
MX (Mail Exchange) records direct email to a mail server. You would set an MX record for 'mail.yourdomain.co.za' to ensure emails are routed to the correct server.
TXT Record
TXT records allow you to add text information to your domain. These are often used for domain verification and email security settings like SPF and DKIM.
NS Record
NS (Name Server) records specify the authoritative name servers for your domain. These are typically set to 'ns1.geeklab.host' and 'ns2.geeklab.host' for GHost Cloud hosting.
SRV Record
SRV (Service) records define the location of servers for specific services. These are often used for configuring services like SIP or LDAP.
Common tasks
One common task is pointing a subdomain to a different server. To do this, create an A record for the subdomain in the Zone Editor, specifying the IP address of the target server. For example, if you want 'blog.yourdomain.co.za' to point to a different server, create an A record with 'blog' as the name and the server's IP address as the destination.
Another task is verifying domain ownership, which often requires adding a TXT record. If a service asks you to verify your domain, they will provide a specific TXT record value to add. Enter the provided value in the Zone Editor under a new TXT record entry.
TTL
TTL (Time to Live) is the duration that a DNS record is cached by DNS servers and clients. Lowering the TTL value before making DNS changes ensures that the changes propagate more quickly. After the changes have propagated, you can increase the TTL to reduce the load on your DNS servers by decreasing the frequency of DNS lookups.
DNS propagation
DNS propagation refers to the time it takes for changes to DNS records to be updated across the internet. This process can take anywhere from 1 to 24 hours, depending on various factors such as the TTL settings and the DNS servers involved. You can use tools like DNS Checker to monitor the propagation status of your DNS changes.
Troubleshooting
If your DNS changes are not taking effect, first ensure that you have saved the changes correctly in the Zone Editor. Check the TTL settings to see if they are too high, which could delay propagation. If email stops working after a DNS change, verify that your MX records are correct and pointing to the right mail server. A common issue when adding a CNAME record is a conflict with an existing record; ensure there are no conflicting records for the same subdomain.
dig or nslookup commands in your terminal to verify DNS records from different locations, helping you troubleshoot propagation issues.Related guides
- How to Log In to cPanel
- Email Deliverability - SPF, DKIM, and DMARC Explained
- How to Install and Manage SSL Certificates
- How to Point Your Domain to GHost Cloud
For reliable hosting solutions that support seamless DNS management, explore our shared hosting plans today.
