Overview

DNS (Domain Name System) records control how a domain and its subdomains connect to websites, email services, and other online services.

If your domain is using Prabhu Host's nameservers, you can manage its DNS records through the DNS Zone Editor in cPanel.

Common DNS records include:

• A Record

• AAAA Record

• CNAME Record

• MX Record

• TXT Record

• SRV Record

Important: DNS records added in Prabhu Host's DNS Management panel will only be publicly effective when the domain is using the nameservers that serve that DNS zone. If your domain uses Cloudflare or another custom DNS provider, manage the records through that provider instead.

How to Access DNS Zone Editor

Step 1: Log in to cPanel

Log in to your Prabhu Host cPanel account.

Step 2: Open Zone Editor

From the cPanel dashboard, navigate to:

Domains → Zone Editor

Step 3: Select Your Domain

Locate the domain for which you want to manage DNS records.

Click Manage next to the domain.

You will see the existing DNS records for the domain.

Adding a DNS Record

Click Add Record and select the required record type.

Enter the required information and save the record.

The exact fields shown may vary depending on the record type.

1. A Record

An A record points a domain or subdomain to an IPv4 address.

Example

Type: A
Name: example.com
Address: 75.2.60.5
TTL: 7200

For a subdomain:

Type: A
Name: app.example.com
Address: 75.2.60.5

A records are commonly used to point a website or subdomain to a web server.

2. AAAA Record

An AAAA record points a domain or subdomain to an IPv6 address.

Example

Type: AAAA
Name: example.com
Address: 2001:db8::1

Use an AAAA record only when the destination server provides an IPv6 address.

3. CNAME Record

A CNAME record points one hostname to another hostname.

Example

Type: CNAME
Name: www.example.com
Target: example.com

This allows:

www.example.com

to follow the DNS destination of:

example.com

Important: A CNAME record should point to a hostname, not directly to an IP address.

4. MX Record

An MX (Mail Exchange) record specifies which mail server receives email for your domain.

Example

Type: MX
Name: example.com
Priority: 10
Destination: mail.example.com

When multiple MX records are configured, the priority determines which mail server should be preferred. A lower priority number has higher preference.

Important: Do not change MX records unless you know which email service your domain is using. Incorrect MX records can cause email delivery problems.

5. TXT Record

TXT records store text-based information associated with a domain.

They are commonly used for:

• SPF

• DKIM

• DMARC

• Domain verification

• Third-party service verification

Example

Type: TXT
Name: example.com
Value: v=spf1 a mx ~all

Another common example is a verification record:

Type: TXT
Name: example.com
Value: verification-code=example123

Always use the exact TXT value provided by the service you are configuring.

6. SRV Record

SRV records specify the hostname and port of a service.

They are commonly used by applications and communication services that require service discovery.

Example

Service: _service
Protocol: _tcp
Name: example.com
Priority: 10
Weight: 5
Port: 443
Target: service.example.com

Use the exact values provided by the application or service provider.

Example: Pointing a Domain to a Website

Suppose your website provider gives you the IP address:

75.2.60.5

You can create:

A Record
Name: example.com
Address: 75.2.60.5

For www, you could use:

CNAME
Name: www.example.com
Target: example.com

This results in:

example.com → 75.2.60.5
www.example.com → example.com → 75.2.60.5

Important: Check Your Nameservers First

Before adding or modifying DNS records, confirm where your domain's DNS is actually managed.

You can check the authoritative nameservers using:

dig NS example.com

If the domain is using Prabhu Host's authoritative nameservers, records can be managed through the corresponding Prabhu Host DNS management interface.

If the domain is using:

• Cloudflare nameservers

• Amazon Route 53

• Another hosting provider

• Another DNS provider

then the DNS records should generally be managed through that provider.

Example

If your domain uses:

ns1.example-dns-provider.com
ns2.example-dns-provider.com

adding a record only inside Prabhu Host's DNS panel will not make that record authoritative on the internet.

Verifying a DNS Record

After adding a record, you can verify it using dig.

Check an A record

dig example.com

Check a specific nameserver

dig @ns1.example.com example.com

Check using Google DNS

dig @8.8.8.8 example.com

Check using Cloudflare DNS

dig @1.1.1.1 example.com

Compare the returned IP address or record with the value you configured.

DNS Propagation

DNS changes may not appear everywhere immediately.

The time required can depend on:

• TTL

• DNS caching

• Recursive DNS resolvers

• The previous DNS record

• Nameserver changes

If the record works from the authoritative nameserver but is not yet visible through public DNS resolvers, it may still be propagating or cached.

Important Precautions

Before modifying DNS records:

• Make sure you are editing the correct domain.

• Check the existing records before making changes.

• Do not delete existing records unless you understand their purpose.

• Be especially careful with MX, SPF, DKIM, and DMARC records because they can affect email delivery.

• Use the exact values provided by your website, email, or third-party service provider.

• If you are unsure about a DNS record, contact Prabhu Host Support before changing it.

Need Help?

If you are unsure which DNS record to add or what value to use, contact Prabhu Host Support with the required record type, hostname, and destination/value provided by your service provider.