How to Manage DNS Settings Through My Hosting Provider's Control Panel

DNS controls how visitors, browsers, and email systems find the services connected to your domain. A single incorrect entry can send users to the wrong server, interrupt email delivery, or prevent domain verification. Ruachost provides accessible DNS management tools through its Client Area and cPanel, allowing you to review and update these settings without working directly with a DNS server.

Introduction to DNS and Its Importance#

The Domain Name System (DNS) translates readable domain names, such as example.com, into the technical destinations computers use. When someone enters your domain in a browser, DNS tells the browser which server hosts your website. DNS also identifies where email should be delivered and helps third-party services verify that you control a domain.

A domain’s DNS information is stored in a DNS zone. That zone contains individual records for your website, subdomains, email services, security policies, and verification requirements.

Effective DNS management matters for several reasons:

• Website availability: A correct A or CNAME record directs visitors to the appropriate web server.
• Email reliability: MX and TXT records help route messages and authenticate outgoing mail.
• Security: SPF, DKIM, and DMARC policies can reduce email spoofing and improve trust.
• Service verification: Search platforms, business applications, and other services may request a TXT or CNAME record.
• Controlled migrations: DNS changes let you move a website or email service without changing the domain people use.

The authoritative nameservers determine where you must manage these records. If your domain uses Ruachost’s nameservers, changes should be made through Ruachost. If it uses another DNS provider’s nameservers, editing records in Ruachost may have no public effect.

Ruachost’s default nameservers are:

• nsa.ruachost.com
• nsb.ruachost.com

A domain does not have to be registered with Ruachost to use them. You can retain your current registrar while pointing the domain to Ruachost for DNS and hosting management, as explained in the guide to using an externally registered domain with Ruachost.

Accessing Ruachost's Control Panel#

Ruachost customers may encounter two related management interfaces: the Client Area and cPanel. They serve different purposes.

The Client Area handles account-level services, while cPanel contains tools associated with a shared hosting account. Ruachost’s shared hosting quick-start guide provides more context about these interfaces.

To access DNS management through the Client Area:

1. Sign in to the Ruachost Client Area.
2. Open Domains.
3. Select Manage DNS.
4. Find the relevant domain using the list or search function.
5. Select the edit or pencil icon beside it.

If the domain does not appear, look for Add DNS Zone. Select the domain and provide the required destination IP address, normally the IP assigned to your hosting account.

For a domain registered with Ruachost, you can review its nameservers under Domains → My Domains. Select Manage, open Nameservers, and confirm that the default nameservers are selected if Ruachost will manage the complete DNS zone.

If the domain is registered elsewhere, change its nameservers through the current registrar. Choose its custom nameserver option, remove obsolete entries, and enter Ruachost’s two default nameservers. The Ruachost nameserver instructions cover this process in more detail.

Before changing nameservers, save a copy of all existing records—especially MX, SPF, DKIM, and DMARC entries. You will need to reproduce them in the new DNS zone if website and email services are split between providers.

Navigating to the DNS Settings Section#

On shared hosting, sign in to cPanel and find the Domains section. Depending on the interface version and available features, the relevant tool may be labelled Zone Editor or DNS Zone Editor. Ruachost’s cPanel resources also cover hosting tools such as MX configuration and email autodiscovery records.

Inside the Zone Editor:

1. Locate the domain you want to manage.
2. Select Manage or the available record-management option.
3. Review the existing zone before making changes.
4. Use the record-type filter if you need to find an A, CNAME, MX, or TXT entry.
5. Confirm that you have selected the correct domain, especially if the hosting account contains several websites.

There are two valid approaches when connecting an externally registered domain:

With the first approach, all public DNS records must exist in the Ruachost zone. With the second, you update records at the current authoritative DNS provider, even though the website itself is hosted by Ruachost.

You can confirm which system is authoritative by checking the domain’s current NS records. Do this before troubleshooting an apparently ignored change; modifying a non-authoritative copy of a zone will not alter where public traffic goes.

Understanding Different Types of DNS Records#

Each DNS record has a specific function. Before editing one, identify the hostname, record type, destination, and TTL requested by your hosting or service provider.

These records are not interchangeable. For example, an MX record routes email rather than web traffic, while a TXT record can publish authentication policies but cannot direct a browser to a server.

A few details deserve particular attention:

• The root domain may appear as @, the full domain, or a blank name field, depending on the interface.
• A CNAME should normally point to a hostname, not an IP address.
• MX records usually require a priority value. A lower number represents a higher preference.
• TXT values must be copied accurately. Missing characters or unintended quotation marks can invalidate a verification or authentication record.
• NS and SOA records are generally managed automatically. Avoid changing them unless you have precise instructions.

TTL, or Time to Live, tells recursive DNS systems how long they may cache a response. A shorter TTL can help planned changes become visible sooner after cached data expires, while a longer TTL reduces how often records need to be requested. However, lowering a TTL after a migration begins will not immediately clear data already cached under the previous value.

Steps to Edit, Add, or Delete DNS Records#

Begin by recording the current configuration. A screenshot or exported zone can help you restore a working value if an update causes unexpected behaviour.

Adding a record#

1. Open the appropriate domain in Manage DNS or the cPanel Zone Editor.
2. Select the option to add a record.
3. Choose the requested record type.
4. Enter the name or hostname. For example, a service might ask you to create a record for www, mail, or a verification-specific label.
5. Enter the destination or value exactly as supplied.
6. Set the priority if you are adding an MX record.
7. Leave the default TTL unless you have a reason to change it.
8. Save the record and verify that it appears in the zone.

Editing an existing record#

Find the record by filtering the list or matching both its name and type. Select Edit, replace only the required fields, and save the change. Avoid altering unrelated records during the same update; isolated changes are easier to test and reverse.

When moving a website, the usual task is to update the A record for the root domain. You should also check whether www has its own A record or a CNAME. Updating only one may cause the root domain and www version to open different servers.

Deleting a record#

Delete a record only after confirming that no active service depends on it. An unfamiliar TXT record might support domain verification, while a CNAME could be used by a business application.

Select the record, choose Delete, and confirm the action. If you are replacing it, add and validate the replacement before removing the old entry where the configuration permits.

After any operation, test the affected service rather than assuming that a successful save means the change is already visible worldwide. DNS caches may continue serving the previous response until its TTL expires.

Troubleshooting Common DNS Issues#

DNS changes can begin appearing quickly, but full propagation may take longer. Ruachost advises that nameserver updates can require up to 24–48 hours to become visible across different networks. During that period, two users may receive different answers for the same domain.

The first troubleshooting step should be confirming authority: does the domain actually use nsa.ruachost.com and nsb.ruachost.com? If not, make the record change wherever the active nameservers are managed.

Next, inspect the zone for typographical errors and conflicts. Check for an incorrect IP address, duplicate entries, missing MX priorities, or a hostname entered twice. Do not delete records simply because they look unfamiliar.

DNSSEC requires special care. If DNSSEC is enabled with the current registrar, disable it before changing nameservers unless valid replacement DNSSEC information has been prepared. An outdated DS record can cause validating resolvers to reject otherwise correct DNS responses. Ruachost highlights this precaution in its guide to pointing a domain from another registrar.

If email fails after a nameserver switch, compare the new zone with the old one. Restore the required MX records and any associated SPF, DKIM, DMARC, autodiscovery, or verification records.

Tips for Optimizing DNS Performance#

Good DNS management is less about making frequent changes and more about maintaining a clean, intentional zone.

• Plan migrations in advance. Lower the relevant TTL before a scheduled move, preferably while the old TTL still has time to expire.
• Keep only necessary records. Remove confirmed obsolete entries, but document their purpose before deletion.
• Use consistent hostnames. Decide how the root domain and www should behave, then configure both intentionally.
• Avoid unnecessary nameserver changes. Record-level updates usually create less disruption when only one service is moving.
• Protect email configuration. Preserve MX and authentication records whenever changing DNS providers.
• Document every update. Note the previous value, new value, time of change, and reason.
• Review access security. Use a strong, unique password for the Client Area and cPanel, and restrict administrative access to trusted users.
• Test from more than one network. Local caching can make a correct change appear unsuccessful—or make an incomplete migration appear finished.

Ruachost operates infrastructure across multiple data-centre locations, including Frankfurt, Amsterdam, Paris, and Seattle, according to its company overview. DNS should still direct each hostname to the exact server destination assigned to your account rather than to an assumed location or address.

Conclusion and Advantages of Using Ruachost#

Managing DNS becomes much safer when you first identify the authoritative nameservers, preserve existing records, and change only what the service requires. Ruachost gives customers both account-level domain controls and cPanel’s Zone Editor, making it possible to manage website routing, email records, subdomains, and verification entries from familiar interfaces.

Its broader hosting environment also includes free SSL certificates, automatic backups, and security tools, while Ruachost plants a tree for every hosting plan. Most importantly for DNS administration, its help resources explain how to connect domains registered elsewhere, switch nameservers, and avoid problems involving email or DNSSEC.

Ready to manage your domain and hosting from one place? Visit Ruachost or follow its domain-pointing guide to get started.