Navigating the backend of your website can sometimes feel like deciphering a secret code, and DNS records are often at the heart of that mystery. If you’ve ever wondered how your domain name magically leads users to your website, or how your emails find their way to the right inbox, you’re thinking about DNS. For Hostinger users, managing these crucial settings is straightforward once you know where to look and what each record does.
This in-depth guide will demystify DNS records on Hostinger, taking you from the basics to advanced management. Whether you’re setting up a new website, configuring email, or troubleshooting connectivity issues, mastering Hostinger’s DNS Zone Editor is an essential skill. By the end of this post, you’ll be able to confidently add, edit, and delete DNS records, ensuring your online presence runs smoothly and efficiently.
Table of Contents
- What Are DNS Records and Why Do They Matter?
- Understanding Common DNS Record Types
- Accessing the DNS Zone Editor in Hostinger
- How to Add and Edit A Records on Hostinger
- How to Add and Edit CNAME Records on Hostinger
- How to Add and Edit MX Records on Hostinger
- How to Add and Edit TXT Records on Hostinger
- Managing NS Records and Domain Nameservers
- Understanding DNS Propagation: The Waiting Game
- Common DNS Management Issues and Troubleshooting
- Advanced DNS Management Tips
- Frequently Asked Questions (FAQ)
What Are DNS Records and Why Do They Matter?
Imagine the internet as a massive phonebook. When you type a domain name like yourwebsite.com
into your browser, it’s like looking up a name in that phonebook. But computers don’t understand names; they understand numbers – specifically, IP addresses. The Domain Name System (DNS) is the internet’s distributed directory service that translates human-readable domain names into machine-readable IP addresses.
DNS records are the individual entries within this directory. They tell web browsers, mail servers, and other internet services where to send requests for your domain. Without correctly configured DNS records, your website wouldn’t load, your emails wouldn’t be delivered, and your subdomains wouldn’t function. Managing your DNS records on Hostinger is therefore critical for the accessibility and functionality of your entire online presence.
Understanding Common DNS Record Types
Different DNS record types serve different purposes. Here’s a breakdown of the most common ones you’ll encounter and manage in Hostinger:
Record Type | Purpose | Example |
---|---|---|
A Record | (Address Record) Maps a domain or subdomain to an IPv4 address. This is typically how your domain points to your web server. | yourdomain.com -> 192.0.2.1 |
AAAA Record | (IPv6 Address Record) Maps a domain or subdomain to an IPv6 address. Similar to an A record but for the newer IPv6 protocol. | yourdomain.com -> 2001:0db8:85a3:0000:0000:8a2e:0370:7334 |
CNAME Record | (Canonical Name Record) Aliases one domain or subdomain to another domain name. Useful for pointing www.yourdomain.com to yourdomain.com or for connecting subdomains to external services. | www.yourdomain.com -> yourdomain.com or blog.yourdomain.com -> yourblogplatform.com |
MX Record | (Mail Exchanger Record) Specifies the mail servers responsible for accepting email messages on behalf of your domain. Includes a “priority” value to dictate the order in which mail servers should be tried. | yourdomain.com MX mail.yourdomain.com (Priority 10) |
TXT Record | (Text Record) Stores plain text information. Commonly used for domain verification (e.g., Google, Microsoft), SPF (Sender Policy Framework) for email authentication, DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting & Conformance). | yourdomain.com TXT "v=spf1 include:_spf.google.com ~all" |
NS Record | (Name Server Record) Designates the authoritative DNS servers for a domain. These records tell the internet which servers hold the master DNS records for your domain. Often managed at your domain registrar. | yourdomain.com NS ns1.hostinger.com |
SRV Record | (Service Record) Specifies the location of services, such as SIP (Voice over IP) or XMPP (Jabber). Not as commonly used for standard website setups but crucial for specific applications. | _sip._tcp.yourdomain.com SRV 10 60 5060 sipserver.yourdomain.com |
Accessing the DNS Zone Editor in Hostinger
Hostinger provides a user-friendly interface called hPanel, which makes managing your DNS records a breeze. Here’s how you can access the DNS Zone Editor:
- Log in to Your Hostinger Account: Go to the Hostinger website and enter your credentials.
- Navigate to the Hosting Section: Once logged in, you’ll be on your hPanel dashboard. If you have multiple hosting plans, select the one associated with the domain you want to manage.
- Find the DNS Zone Editor: In the left-hand sidebar, look for the “Advanced” section. Click on it to expand, then select “DNS Zone Editor”.
Visual Description: You’ll see the hPanel dashboard with a clear navigation menu on the left. The “DNS Zone Editor” option will be visible under a section like “Advanced” or directly in the main menu, often accompanied by an icon resembling a globe or DNS symbols.
This is your central hub for all DNS record management for the selected domain.
How to Add and Edit A Records on Hostinger
An A record is fundamental as it points your domain or subdomain to a specific IPv4 address, which is typically where your website’s server resides.
To Add an A Record:
- Access DNS Zone Editor: Follow the steps above to get to the DNS Zone Editor.
- Locate the “Add new record” Section: Scroll down slightly, and you’ll find a section dedicated to adding new records.
- Select A Record Type: From the “Type” dropdown, choose “A”.
- Enter “Name”:
- For your main domain (e.g.,
yourdomain.com
), leave this field blank or enter@
. Hostinger often auto-populates it correctly. - For a subdomain (e.g.,
blog.yourdomain.com
), enter the subdomain part (e.g.,blog
).
- For your main domain (e.g.,
- Enter “Points to”: This is where you put the IPv4 address of your server. Your hosting provider (if external) or your own server’s IP will provide this.
- Set “TTL” (Time to Live): This value tells DNS resolvers how long to cache the record before querying for a new one. Default is usually
14400
seconds (4 hours), which is generally fine. For faster updates during troubleshooting, you can temporarily lower it (e.g.,300
seconds), but remember to set it back later. - Click “Add Record”: Your new A record will now be listed.
Visual Description: Within the DNS Zone Editor, there’s a clear form with dropdowns for “Type,” input fields for “Name” and “Points to,” and a “TTL” field. A prominent “Add Record” button finalizes the process.
To Edit an Existing A Record:
- Access DNS Zone Editor: Go to the DNS Zone Editor.
- Find the Record: Scroll through the list of existing DNS records until you find the A record you wish to modify.
- Click “Edit”: On the right side of the record entry, you’ll see an “Edit” button (often a pencil icon).
- Make Changes: Modify the “Points to” IP address or “TTL” as needed.
- Click “Update”: Save your changes.
Tip: If you’re pointing your domain to Hostinger’s hosting, the A records are usually set up automatically. You’ll primarily use this feature when pointing your domain registered at Hostinger to an external web host, or when setting up custom subdomains that need specific IP addresses.
How to Add and Edit CNAME Records on Hostinger
CNAME records create an alias from one domain name to another. They are incredibly useful for linking www.yourdomain.com
to yourdomain.com
or for pointing subdomains to services like Shopify, ClickFunnels, or various SaaS platforms.
To Add a CNAME Record:
- Access DNS Zone Editor.
- Select CNAME Record Type: Choose “CNAME” from the “Type” dropdown.
- Enter “Name”: This is the subdomain or alias you want to create (e.g.,
www
,blog
,shop
). Do not include your domain name here, just the alias itself. - Enter “Points to”: This is the target domain or subdomain that your alias will point to (e.g.,
yourdomain.com
,shops.shopify.com
,ghs.google.com
). - Set “TTL”: Default is usually fine.
- Click “Add Record”.
Visual Description: Similar to adding an A record, but the “Type” is “CNAME” and the “Points to” field expects a domain name instead of an IP address.
To Edit an Existing CNAME Record:
- Access DNS Zone Editor.
- Find the Record: Locate the CNAME record in the list.
- Click “Edit”.
- Make Changes: Update the “Points to” domain or “TTL”.
- Click “Update”.
Common Use Case: If you want www.yourdomain.com
to go to yourdomain.com
, you’d add a CNAME record where “Name” is www
and “Points to” is yourdomain.com
.
How to Add and Edit MX Records on Hostinger
MX records are crucial for email delivery. They tell other mail servers where to send emails for your domain. Incorrect MX records can lead to emails not being received.
To Add an MX Record:
- Access DNS Zone Editor.
- Select MX Record Type: Choose “MX” from the “Type” dropdown.
- Enter “Name”: For your main domain’s email, leave this blank or enter
@
. - Enter “Points to”: This is the mail server address provided by your email service (e.g.,
aspmx.l.google.com
for Google Workspace, ormail.yourdomain.com
if using Hostinger’s email). - Set “Priority”: This is a numerical value (e.g., 1, 5, 10, 20). Lower numbers indicate higher priority. If you have multiple MX records, the mail server will try the lowest priority first.
- Set “TTL”: Default is usually fine.
- Click “Add Record”.
Visual Description: The MX record addition form includes an extra “Priority” field alongside “Name,” “Points to,” and “TTL.”
To Edit an Existing MX Record:
- Access DNS Zone Editor.
- Find the Record: Locate the MX record in the list.
- Click “Edit”.
- Make Changes: Modify the “Points to” server, “Priority,” or “TTL.”
- Click “Update”.
Important: If you’re using an external email service like Google Workspace or Zoho Mail, you’ll need to add all their required MX records (they often provide multiple with different priorities). Always double-check the exact values provided by your email provider.
How to Add and Edit TXT Records on Hostinger
TXT records are versatile and primarily used for verification and authentication purposes. Common uses include:
- Domain Verification: Proving domain ownership for services like Google Search Console, Microsoft 365, or other web services.
- SPF (Sender Policy Framework): Helps prevent email spoofing by specifying which mail servers are authorized to send email on behalf of your domain.
- DKIM (DomainKeys Identified Mail): Adds a digital signature to outgoing emails, allowing recipients to verify that the email was sent by an authorized server and hasn’t been tampered with.
- DMARC (Domain-based Message Authentication, Reporting & Conformance): Builds upon SPF and DKIM to provide a policy for handling emails that fail authentication and reporting on their status.
To Add a TXT Record:
- Access DNS Zone Editor.
- Select TXT Record Type: Choose “TXT” from the “Type” dropdown.
- Enter “Name”: This varies depending on the purpose.
- For main domain verification/SPF/DMARC: leave blank or enter
@
. - For DKIM: Usually something like
selector._domainkey
(e.g.,google._domainkey
). - For other verifications, the service will specify the exact name (e.g.,
_dmarc
).
- For main domain verification/SPF/DMARC: leave blank or enter
- Enter “Text Value”: This is the long string of text provided by the service you’re verifying or the SPF/DKIM/DMARC record itself. Ensure you copy it precisely, including quotes if specified.
- Set “TTL”: Default is usually fine.
- Click “Add Record”.
Visual Description: The TXT record form requires a “Name” and a larger “Text Value” input field, as these records can contain quite a bit of information.
To Edit an Existing TXT Record:
- Access DNS Zone Editor.
- Find the Record: Locate the TXT record in the list.
- Click “Edit”.
- Make Changes: Modify the “Text Value” or “TTL.”
- Click “Update”.
Tip: Always copy and paste TXT record values directly from the service that provides them to avoid typos, which can invalidate the record.
Managing NS Records and Domain Nameservers
NS (Nameserver) records designate the authoritative DNS servers for your domain. While you can see and sometimes modify NS records within Hostinger’s DNS Zone Editor, the primary place to change your domain’s nameservers is typically at your domain registrar.
Understanding the Difference:
- Changing Nameservers at your Registrar: This is what you do if you want to completely delegate your domain’s DNS management to Hostinger (or another provider like Cloudflare). You tell the internet where to find the authoritative DNS servers for your domain. For example, if your domain is registered with GoDaddy but hosted on Hostinger, you’d change the nameservers at GoDaddy to Hostinger’s nameservers (
ns1.dns-parking.com
,ns2.dns-parking.com
). Once this is done, all your DNS records (A, CNAME, MX, TXT, etc.) will be managed within Hostinger’s DNS Zone Editor. - Editing NS Records in Hostinger’s DNS Zone Editor: This is less common. If your domain’s nameservers already point to Hostinger, you are managing your DNS through Hostinger. Modifying individual NS records here would typically be for advanced scenarios like delegating a subdomain to another DNS server (e.g.,
sub.yourdomain.com
uses different nameservers). For most users, you won’t need to touch these internal NS records.
When to Change Nameservers (at Registrar):
- When you transfer your website to Hostinger from another host, but your domain remains at a different registrar.
- When you want to use a third-party DNS service (e.g., Cloudflare) to manage your DNS, even if your domain is registered and hosted with Hostinger.
Hostinger’s Default Nameservers:
If your domain is hosted with Hostinger, your nameservers should typically be:
ns1.dns-parking.com
ns2.dns-parking.com
Visual Description: In hPanel, under “Domains” or “Hosting,” there’s usually a “Nameservers” section where you can view or change your domain’s primary nameservers if your domain is registered with Hostinger. If your domain is external, you’d make this change on your registrar’s website.
Understanding DNS Propagation: The Waiting Game
After you make any changes to your DNS records, those changes aren’t instantly reflected across the entire internet. This delay is known as DNS propagation.
What Happens During Propagation?
When you update a DNS record, the change needs to be updated on your authoritative nameservers first. Then, internet service providers (ISPs) and other DNS servers around the world, which cache DNS information to speed up requests, need to update their cached records with the new information.
Factors Affecting Propagation Time:
- TTL (Time to Live): The TTL value of a record determines how long DNS resolvers should cache that record. A lower TTL means changes will propagate faster (as caches expire more quickly), but it also means more frequent queries to your DNS server. A typical TTL is 14400 seconds (4 hours).
- ISP Caching: Some ISPs cache records for longer than the TTL, which can cause delays.
- Geographic Location: Changes often propagate regionally first before becoming global.
How Long Does it Take?
DNS propagation can take anywhere from a few minutes to 24-48 hours, although it’s often much quicker (within a few hours) for common record types on well-configured DNS systems like Hostinger’s.
How to Check DNS Propagation:
You can use online tools to check the status of your DNS propagation. Popular tools include:
- What’s My DNS?:
https://www.whatsmydns.net/
- DNS Checker:
https://dnschecker.org/
Simply enter your domain name and select the record type you’re checking, and these tools will query DNS servers worldwide to show you where your changes have updated.
Common DNS Management Issues and Troubleshooting
Even with careful management, you might encounter issues. Here are some common problems and how to troubleshoot them:
- Website Not Loading or Showing Old Content:
- Cause: DNS propagation is still ongoing, or your local DNS cache needs to be cleared.
- Solution: Wait for propagation. Clear your browser cache and your operating system’s DNS cache (e.g.,
ipconfig /flushdns
on Windows,sudo killall -HUP mDNSResponder
on macOS). Checkwhatsmydns.net
to see if the A record has updated globally.
- Email Not Sending/Receiving:
- Cause: Incorrect MX records, missing SPF/DKIM/DMARC TXT records, or issues with your mail server.
- Solution: Double-check all MX, SPF, DKIM, and DMARC records against your email provider’s exact specifications. Ensure priorities are correct for MX records. Verify your email client settings.
- Subdomain Not Resolving:
- Cause: Missing or incorrect A or CNAME record for the subdomain.
- Solution: Ensure you have an A record pointing the subdomain to the correct IP address or a CNAME record pointing it to the correct target domain.
- SSL Certificate Issues (e.g., “Not Secure” warning):
- Cause: Often related to the domain not pointing correctly to the server where the SSL is installed, or specific DNS verification (like a CNAME or TXT record for Let’s Encrypt DNS-01 challenge) is missing.
- Solution: Verify your A record points to the correct server. If using a DNS-01 challenge for SSL, ensure the required TXT/CNAME record is correctly added and propagated.
- Incorrect Record Values:
- Cause: Typos in IP addresses, domain names, or text values.
- Solution: Always copy-paste complex values. Double-check every character against the source.
- Conflicting Records:
- Cause: Having multiple A or CNAME records for the same “Name” can lead to unpredictable behavior. For example, a domain cannot have both an A record and a CNAME record for the same hostname.
- Solution: Remove redundant or conflicting records. Keep only the one that serves the intended purpose.
When troubleshooting, patience is key. DNS changes take time, so making multiple changes in quick succession can complicate diagnosis. Make one change, wait for propagation, then test.
Advanced DNS Management Tips
For those looking to optimize their DNS setup further, here are a few advanced tips:
- Using Cloudflare for DNS: Even if your hosting is with Hostinger, you can use Cloudflare’s free DNS service. Cloudflare offers faster DNS resolution, enhanced security (DDoS protection, WAF), and a global CDN. To use it, you’d change your domain’s nameservers at your registrar to Cloudflare’s nameservers, and then manage all your A, CNAME, MX records within Cloudflare’s dashboard.
- DNSSEC (DNS Security Extensions): DNSSEC adds a layer of security to DNS by digitally signing DNS records. This helps prevent DNS spoofing and ensures that the DNS data you receive is authentic. Hostinger typically supports DNSSEC, and you can usually enable it from your domain management section or within Cloudflare.
- Lowering TTL for Planned Changes: If you anticipate needing to make a critical DNS change that requires rapid propagation (e.g., switching hosts during off-peak hours), you can temporarily lower the TTL of relevant records (e.g., to 300 seconds) a day or two before the change. This ensures that when you make the actual switch, the new records will propagate much faster once old caches expire. Remember to revert to a higher TTL (like 14400) afterward to reduce DNS server load.
- Understanding Wildcard Records: A wildcard record (
*
) allows you to point any unspecified subdomain to a specific IP address or domain. For example,*.yourdomain.com
A192.0.2.1
would meananything.yourdomain.com
would resolve to that IP unless a more specific record exists. Use with caution, as it can sometimes catch unintended subdomains.
Frequently Asked Questions (FAQ)
Q1: How long does DNS propagation take?
DNS propagation typically takes a few minutes to several hours, but it can extend up to 24-48 hours in some cases due to various caching mechanisms across the internet.
Q2: Can I host my DNS elsewhere (e.g., Cloudflare) and my website on Hostinger?
Yes, absolutely. You would change your domain’s nameservers at your domain registrar to point to Cloudflare’s nameservers. Then, within your Cloudflare DNS settings, you would create the necessary A and CNAME records to point to your Hostinger server’s IP address.
Q3: What happens if I delete a DNS record by mistake?
If you accidentally delete a critical DNS record (like an A record for your domain or an MX record for your email), your website or email service may stop working once the old cached records expire. You should immediately re-add the correct record.
Q4: What’s the difference between an A record and a CNAME record?
An A record maps a domain/subdomain directly to an IP address. A CNAME record aliases a domain/subdomain to another domain name. You cannot have both an A record and a CNAME record for the exact same hostname (e.g., yourdomain.com
cannot have both an A and CNAME record).
Q5: Do I need to manage DNS if my domain is registered with Hostinger?
If your domain is registered with Hostinger and uses Hostinger’s default nameservers, you will manage all your DNS records directly through the Hostinger hPanel DNS Zone Editor. The initial setup for your website (A records) is often automatic.
Q6: How do I point my domain to an external service like Shopify or Google Workspace?
For external services, you’ll typically need to add specific CNAME or TXT records as provided by that service. For example, Shopify often requires a CNAME record for www
and possibly an A record for your root domain. Google Workspace will require specific MX and TXT (SPF/DKIM/DMARC) records.
Q7: What is TTL (Time to Live) in DNS records?
TTL stands for Time to Live. It’s a value (in seconds) that tells DNS resolvers how long to cache a DNS record before querying for an updated version. A higher TTL means faster subsequent lookups but slower propagation of changes. A lower TTL means faster propagation but potentially more queries.
Q8: Can I use different nameservers for my domain and still use Hostinger hosting?
Yes. If your domain is registered with another provider or you prefer to use a third-party DNS service (like Cloudflare), you would change your domain’s nameservers at your registrar to point to your chosen DNS service. Then, within that service’s DNS manager, you’d add A records that point to your Hostinger server’s IP address.
Managing DNS records on Hostinger might seem daunting at first, but with the comprehensive tools available in hPanel and a clear understanding of each record type, you gain powerful control over your online presence. From ensuring your website loads correctly to guaranteeing seamless email delivery, accurate DNS configuration is foundational.
Remember to always double-check your entries, be patient during propagation, and leverage resources like online DNS checkers when troubleshooting. With these practices, you’ll master your domain’s DNS settings in no time.
Ready to take control of your domain? Dive into Hostinger’s DNS management features today. If you have any questions or tips to share, we’d love to hear them in the comments below!

लेटेस्ट अपडेट्स, ट्रेंडिंग न्यूज़, वायरल टॉपिक्स, फैशन से जुड़ी जानकारी और बहुत कुछ। मोबाइल लॉन्च, टेक तुलना और ताज़ा मुद्दों पर इन-डेप्थ आर्टिकल्स के साथ हमेशा रहें अपडेटेड