English
Magyar
When changing name servers, it is not just a single setting that changes: the domain’s DNS management is transferred to a new DNS server. If the new environment has not been prepared, the website or email service may be disrupted. Changing the name servers therefore begins with an assessment of the existing DNS data and the preparation of the new zone.
It is not always clear whether a change should be made via the domain registrar’s interface or the hosting control panel. The two interfaces serve different purposes: name server settings are typically linked to the domain, whilst cPanel is used to configure the hosting and the DNS records managed there. Before making the change, make a note of the existing records, particularly if you wish to continue using your email service as normal.
In this guide, you’ll learn the difference between name servers and DNS records, as well as how to prepare for and carry out the migration in a safe and orderly manner. We’ll show you how to check the new settings, what to expect during the propagation period, and when it’s worth troubleshooting. We’ll also cover the technical checks required for .hu domains.
What does changing the name server mean, and what changes as a result?
Name servers specify which DNS server is responsible for domain queries, i.e. where the DNS data associated with the domain can be found. The DNS server links the domain name to the data for the associated services. Based on this, the browser, for example, finds the website address, whilst the email system determines where to deliver messages. Changing the name server therefore involves specifying which DNS server should manage the domain’s zone.
Domain registration and web hosting are separate services, linked via DNS settings. Domain registration secures the domain name, whilst hosting provides space for website files and other services. The two services can also be managed via separate interfaces. cPanel is used to manage hosting; it is not the standard place for modifying name servers.
Name servers and DNS records: what’s the difference?
A name server points to the server responsible for the domain’s DNS zone. The records in the zone determine which data is associated with each service. The summary entitled ‘How Name Servers Work in the DNS’ also explains the role name servers play in name resolution.
- An A record maps a name to an IPv4 address.
- The AAAA record specifies an IPv6 address.
- The MX record specifies the destination for email associated with the domain.
When a record is updated, only the target in question changes, whilst the management of the DNS zone can remain in the same place. Replacing the name servers, on the other hand, transfers the entire zone management to a different DNS server. Simply specifying the new name servers does not, in itself, create the A, AAAA or MX records. These must also be included in the new zone; otherwise, the website or email service may not function correctly.
When might you need to change your name servers?
When switching hosting providers, you may need to change your name servers if you wish to manage the domain’s entire DNS zone within the new environment. It may also be necessary if you transfer your DNS management to another service provider. If you are only changing your website address or email settings, it may be sufficient to update the relevant records whilst leaving the name servers unchanged.
Transferring a domain does not, in itself, change the name servers. Registration affects the service provider managing the domain, whilst the name server settings determine where the DNS zone is managed. Before switching, obtain the name server details for the new environment and assess which records you need for your website and email.
During the planning stage, clarify the following in advance:
- which name servers you need to specify for the domain;
- Which A, AAAA and MX records need to be added or retained;
- Does the new DNS zone contain the service data required for it to function?
Before changing your nameservers: what should you check to ensure a secure transition?
During the preparation process, don’t just make a note of the current name servers. Save the important details of the DNS zone so that you can compare the old and new settings. You can take a screenshot or make a copy of the records, but check that the values, record types and names are clearly legible.
Before making any changes, make a note of at least the A, AAAA and MX records, as well as the SPF and DKIM details relating to email authentication. Also make a note of which setting belongs to which service. This will make it easier to spot if a record is missing from the new DNS environment or has been accidentally altered.
Assessing the DNS settings for the website and email
The availability of a website is determined by the correct value of the A or AAAA record. Please check that the address used for the website is listed in the new zone. The routing of emails is determined by the MX records. If these are missing or differ from what is required, email delivery may also be affected. Please also retain the SPF and DKIM settings, as these are related to email authentication.
- Set up the A and AAAA records for your website.
- Copy the names and values of the MX records.
- Save your SPF and DKIM records and make a note of which email service they belong to.
- Before the switchover, compare the old zone with the new one.
If the website and email are managed by separate systems, the fact that one is working does not prove that the DNS settings for the other are also correct. It is particularly important to retain the records required for email if the website is being moved but the email service remains unchanged. In such cases, you should also include the email hosting settings in your pre-migration assessment.
Important: the records required for the website, email and other relevant services must also be included in the DNS zone of the new name servers. Changing the name servers does not transfer this data.
Checking the new DNS zone and DNSSEC
Before configuring the new name servers, review the managed zone and check that all necessary records are present. Also take note of the DNSSEC status: the security data stored in the domain registry and on the DNS server must be consistent. The steps involved in the transition depend on your existing settings, so do not apply the same DNSSEC changes to every domain.
Changes may not be immediately visible on all networks. The explanation of DNS propagation summarises why different DNS records may appear during the transition. Preparing in advance helps to distinguish between a temporary update and a missing or incorrect record.
Changing your nameservers or updating your DNS records: which is right for you?
The choice depends on whether you wish to transfer management of the entire domain’s DNS zone elsewhere, or simply change the purpose of a single service. As these two operations affect different areas, you should first clarify exactly which setting you wish to change.
| Action | When is it advisable? | What’s changing? |
|---|---|---|
| Name server change | It would move the entire DNS management to a different environment. | The new name server manages the domain’s DNS zone. |
| Editing a custom record | It would update the purpose of a service. | Only the value of the selected record – such as A, AAAA or MX – changes. |
Understanding the basics and workings of DNS helps you grasp how records are linked to the services assigned to a domain. The right solution depends on where you wish to host and manage the entire DNS zone.
Please also select the relevant functions within the control panels separately. cPanel is the interface for managing your hosting account, where you can manage settings relating to your hosting. The exact location of the nameserver settings within the domain registrar’s interface may vary from provider to provider. cPanel is therefore not the standard location for changing nameservers.
When is it advisable to replace all name servers?
Changing your name servers is appropriate if you want the entire DNS zone for your domain to be managed by a new provider. This is a common option when switching hosting providers, but it is not required for every migration. If you keep your DNS management with your current provider, you may only need to update certain records. Before making a decision, review the contents of the new zone and check that it meets the requirements of your website, email and other services you use.
Compare the new zone with your current settings. If your DNS management remains in one place but the purpose of your hosting changes, updating only the relevant records may be a more targeted solution. This way, you won’t have to transfer the management of the entire zone just because you need to change the address of a single service.
When is it sufficient to change just one DNS record?
If you are simply changing the purpose of your website, it may be sufficient to amend the A or AAAA record. If the email routing changes, please review the MX record. In this case, the name servers can remain unchanged if you can edit the relevant record at your current DNS management site. The aWh DNS records management knowledge base offers relevant guides to help you review the settings.
A website or email outage is not an inevitable consequence of the migration. You can minimise the risk by identifying the necessary changes in advance and ensuring that the records required for operation are also available in the new environment. Before making a decision, consider the following: are you changing the purpose of a single service, or do you wish to transfer the management of the entire DNS zone?
Step-by-step guide to changing name servers in the domain management interface
Name server changes are usually made via the domain management interface. The exact menu options and labels may vary depending on the registrar, so the steps below are intended as a general guide. Before making any changes, please ensure you have the name server details for the target system and the DNS records required for the changeover.
The general procedure for changing name servers
- Log in to your domain control panel. Open your account with the domain registrar where the settings for that domain are managed. If you have multiple domains, first check the name of the domain you have selected.
- Look for the name server settings. The menu item may be called, for example, ‘Name Servers’ or ‘DNS Settings’, but the name of the interface may vary depending on the provider. Do not look for the domain registrar settings in cPanel. cPanel is a web hosting control panel; you should change the domain settings via the control panel associated with the domain.
- Read the new values from the target system. Copy the names of the name servers exactly from where you manage the new DNS zone. Do not add any assumed values, and ensure that you copy the characters exactly.
- Enter the new name servers. Replace the previous values with the details for the target system. Before saving, compare the names you have entered with those in the source and check that there are no typos.
- Save the changes. If the interface asks for confirmation, read the message and then confirm. For .hu domains, the change may also undergo a technical check, so the new name servers must respond correctly to queries about the domain.
- Make a note of the migration details. Write down the time of the backup and the new name servers. This will make it easier to check and troubleshoot any issues later on.
For .hu domains, one of the requirements for registry verification is that there must be at least two name servers with independent IP addresses that provide authoritative responses for the domain. If the change cannot be saved or the verification fails, first check the settings of the new DNS environment; do not repeat the attempt without making any changes.
What should you check immediately after saving?
Check whether the control panel has confirmed the backup and whether the new name servers appear in the domain settings. The change recorded in the control panel and the fact that the result is visible in all queries do not necessarily happen simultaneously. Therefore, the first query showing a discrepancy does not in itself prove that there is an error.
If your website or email is not working, check that the records you previously noted down are present in the new DNS zone. Check the settings for your website and email separately. You can also review the interfaces and options for managing your domain on the domain registration management page. If you are planning to register a new domain, take a look at aWh’s domain registration options.
After changing your nameservers: propagation, verification and next steps
After saving, the updated DNS data may not be immediately visible at all query points. This process is known as DNS propagation: different DNS servers may receive the new data at different times, whilst some locations may still display the previous information. The duration of the transition may depend on previous DNS settings, the TTL values of the records, and the caches of the systems making the queries.
The update can often take anywhere from a few minutes to a few hours, but you may have to wait longer. There is no exact timeframe that applies to all domains and networks. Do not change the settings again simply because a single check still shows the previous data. Compare the results at several different times, then examine each service individually.
How can you check that the new name servers are working?
Check that queries for the domain are now being answered by the new name servers. Then test the services associated with the domain separately. Check in your browser that the website is pointing to the correct destination, and when using email, send and receive test messages. Do not automatically draw conclusions about the status of one service based on the results of a test on another.
- Name servers: does a domain lookup show the new name servers?
- Website: Do the A or AAAA records in the new DNS zone point to the correct destination?
- Email: Are incoming and outgoing emails working, and are the MX records and email authentication details correct?
- DNSSEC: if the domain holder uses this security feature, is its status consistent with the settings of the new name servers?
If you notice any discrepancies between the queries, make a note of which data you received and when. Comparing the results will help you distinguish between an ongoing update and an error in the DNS zone. Bear in mind that the results may also be affected by the caching of the checking tool or your own network.
Common error messages and safe troubleshooting
If the website is unavailable, first check whether the required A or AAAA record is present in the new zone and whether its value matches the details of the target system. In the event of an email error, check the MX records and then compare them with the previously recorded SPF and DKIM details. Do not delete or overwrite other records at random, as this may affect the operation of other services.
When using DNSSEC, please also check that the DNSSEC records associated with the domain are compatible with the new DNS environment. The steps required depend on your existing settings, so do not automatically apply the same changes to every domain. If your website or email still does not work after checking the records, the values you noted down before saving will help you identify which record or setting has changed.
When choosing a new domain or hosting, take a look at aWh’s domain solutions and web hosting options. Domains and hosting are separate services, linked together by the appropriate DNS settings.
Plan your next domain move
Changing your name servers is a good opportunity to review how you manage your online presence. Take stock of the services you use, your access rights and the security settings you check regularly. This will make it easier to plan any future changes and ensure your administration remains transparent.
If you’re looking for a new domain or would like to review your current domain management options, choose the solution that best suits your needs. Among aWh’s domain registration and web hosting options, you’ll find a range of starting points, from cPanel and WordPress hosting to VPS hosting.
Take a look at aWh’s domain registration and web hosting options, and plan the next step for your online presence.
Frequently asked questions about changing name servers
Where should you change your nameservers?
Please change the name servers via the domain management interface at the registrar where your domain settings are accessible. After logging in, check the domain name before making any changes. For secure access, use a strong, unique password and, if available, enable two-factor authentication. cPanel is used to configure your hosting account; it is not the general platform for domain registrar operations.
How long does it take for the name server change to take effect?
There is no fixed deadline that applies to all domains and networks. If the new details have not yet appeared, make a note of the time of the change, then check again later using the same domain name. This will allow you to compare the results. If the registrar’s interface displays an error, or if the setting did not save, do not start troubleshooting by waiting; instead, check whether it was saved.
Will my website still be available after the name server change?
Changing the name servers does not in itself delete the website’s content, but the website’s availability depends on the settings of the new environment. When checking, try opening both the main domain name and the ‘www’ version, if you use both. Check whether the expected page appears or whether a browser error is displayed. Check separately that the website’s files are present on the hosting server.
Does changing the name server affect email functionality?
Yes, this may affect the email associated with the domain, so please check that you can send and receive emails after the changeover. It is important to note that changing the DNS settings will not transfer the contents of your email accounts or any previous messages. If your email runs on a separate system, the accounts and login details will remain linked to that system. During the test, please also send a message from an external address.
What is the difference between changing a name server and updating a DNS record?
Changing the name servers alters where the domain’s DNS is managed, whilst editing a single record only affects a specific setting. First, clarify whether you wish to manage the entire DNS zone in a different environment or simply change the settings for a single service. Before modifying a record, check that the data associated with the other, unchanged services remains accessible.
Is it necessary to perform a transfer of the domain to change the name servers?
No, changing the name servers does not require you to perform a transfer of the domain. The domain can remain with its current registrar whilst DNS management is transferred to another system. Before making any changes, ensure that you have access to the domain’s control panel and have the exact details of the new name servers. This will help you avoid any delays in the transition caused by a lack of access or the necessary information.
Why isn’t my website or email working after changing the name servers?
The cause may be missing or incorrect DNS settings, or it could be a fault with the service itself. First, make a note of the exact error message and whether the website, email or both are affected. Next, compare the results of the service when it is working with those when it is faulty, then check the details of the new zone. If the domain uses DNSSEC, take its settings into account as well. Do not make several random changes at once.