OnlineHostings.in · Powering Your Digital Growth.
Get Started
Home / Domains / DNS Records Guide
DNS RECORDS GUIDE

Understand the records that connect your domain to the internet.

DNS records tell internet services where to find your website, how to deliver email and which systems are authorised to use your domain. Learn what the common record types do before making changes to your DNS zone.

  • Understand A, AAAA, CNAME, MX and TXT records
  • Learn host, value, TTL and priority fields
  • Review email authentication and change precautions
COMMON DNS RECORD TYPES

What each record is used for

The records available in a DNS control panel can vary by provider and DNS service.

A

IPv4 address

Maps a hostname to an IPv4 address, commonly used to direct a website hostname to a server.

AAAA

IPv6 address

Maps a hostname to an IPv6 address when the destination service supports IPv6.

CNAME

Canonical name

Creates an alias from one hostname to another hostname. It generally cannot coexist with other data at the same owner name.

MX

Mail exchange

Identifies the mail servers that receive email for a domain. MX records use priority values to establish preference.

TXT

Text information

Stores text used for domain verification and email authentication policies such as SPF and DMARC.

NS

Name server

Identifies authoritative name servers for a DNS zone or delegated subdomain.

SRV

Service locator

Publishes the hostname, port, priority and weight for supported network services.

CAA

Certificate authority authorisation

Specifies which certificate authorities are permitted to issue certificates for a domain, subject to their validation.

PTR

Reverse DNS

Maps an IP address back to a hostname. Reverse DNS is usually controlled by the IP address provider, not the domain's ordinary DNS zone.

READING A DNS RECORD

Know the fields before you save

Control panels may use slightly different labels, but these are the common record components.

Record fields

  • Name / Host: The domain or subdomain the record applies to, such as the root domain or www.
  • Type: The record category, such as A, MX or TXT.
  • Value / Target: The address, hostname or text data stored in the record.
  • TTL: Time to Live; how long resolvers may cache the record before checking again.
  • Priority: Used by record types such as MX and SRV to express preference or ordering.

Illustrative MX record

TypeMXName@ (root domain)Priority10Targetmail.example.comTTLProvider default

This is a format example only. Replace it with the exact values supplied by your email provider.

EMAIL DNS AUTHENTICATION

SPF, DKIM and DMARC work together

Correct email DNS configuration can help receiving systems assess whether messages are authorised and properly authenticated.

SPF

An SPF policy is published as a TXT record and lists the sending systems authorised by the domain owner. A domain should not publish multiple separate SPF records for the same hostname; consolidate authorised senders into one policy.

DKIM

DKIM uses a public key published in DNS, commonly as a TXT record under a selector-specific hostname. The sending mail system signs messages with the corresponding private key.

DMARC

DMARC is published as a TXT record under _dmarc. It defines how receivers should handle messages that fail DMARC alignment and can specify where aggregate or forensic reports are sent.

Do not copy generic SPF, DKIM or DMARC values into a live domain. Obtain the exact hostnames, keys and policy values from each email service you use. Review all legitimate senders before changing an existing SPF policy.

BEFORE YOU CHANGE DNS

Use a careful change process

Find the authoritative DNS provider

Records must be changed at the provider hosting the active authoritative DNS zone. This may differ from the domain registrar or web host.

Record the current configuration

Export or document existing records before editing. Note which website, mail, verification and third-party services depend on them.

Check conflicts and dependencies

Review CNAME restrictions, duplicate or conflicting records, MX priorities and any delegated subdomains before saving.

Allow for DNS caching

Updates may not appear everywhere immediately. Resolver caches and TTL values influence when changes are observed.

Changing nameservers is different from editing individual DNS records. A nameserver change can move authority for the entire zone; make sure the required records exist at the new DNS provider before switching.

DNS RECORDS FAQ

Frequently asked questions

Are DNS records and nameservers the same?

No. DNS records contain information such as website addresses and mail routing. Nameservers identify the DNS servers that are authoritative for a domain or delegated zone.

Can I use a CNAME record for my root domain?

Traditional DNS rules do not allow a CNAME to coexist with other record data at the same name. Some DNS providers offer provider-specific ALIAS, ANAME or CNAME-flattening features for root domains; check the provider's documentation.

What TTL should I use?

Use a value appropriate to the service and provider guidance. A shorter TTL can help planned changes be picked up sooner after caches expire, but it does not guarantee immediate global propagation.

Will changing an A record affect email?

An A record change for a website hostname does not normally change MX records. However, mail can be affected if you change nameservers, remove mail-related records or alter a hostname used by your mail service.

Can OnlineHostings.in edit my live DNS records from this guide?

No. This page is an educational guide. Live DNS changes require access to the authoritative DNS provider and confirmation of the intended records.

NEED HELP WITH YOUR DNS ZONE?

Get guidance before changing important records.

Share your domain, DNS provider and the service you are connecting. We can help identify the records you should verify with the relevant provider.

Enquire About DNS Records