Learn Plesk

Managing your websites and servers is simple and efficient with the Plesk Web Hosting Control Panel!

• Last Updated: 01/23/2026
• ( 13 minutes reading )

How to manage global DNS settings in Plesk

Introduction

DNS (Domain Name System) is one of the most important components of your hosting environment. It controls how your domains resolve to your server, how email routing is handled, and how external services communicate with your website.

Plesk provides a centralized interface where you can manage server-wide DNS settings, including DNS templates, default DNS zones, DNS server configuration, and how DNS is handled for newly added domains.

Managing global DNS settings ensures consistency across your domains, simplifies DNS management, and helps prevent misconfigurations.

In this tutorial, we will guide you through the process of managing global DNS settings in Plesk.

Getting Started

First and foremost, please ensure you are logged in to your Plesk control panel. To do that, please enter your IP address, hostname, or domain name inside your web browser’s search bar and add “:8443” at the end. It should look something like: “https://yourdomain.com:8443”. By doing so, you will be prompted by a login form that requests your username and password.

plesk-login-screen

After logging in with your username and password, Plesk will automatically display the “Websites & Domains” page, which will serve as the index page from where you can manage everything related to your websites and domains on Plesk.

Accessing Global DNS Settings

To manage DNS on a server-wide level, please click on the “Tools & Settings” option from the left-hand menu.

tools-and-settings

After doing that, please locate the “General Settings” section and, underneath it, please click on  “DNS Settings”.

dns-settings

The DNS Settings are the primary location for configuring how DNS records are created for all domains and for server-wide DNS settings.

dns-settings-options

On that page, you will have complete control over everything related to the DNS service on your Plesk server.

Understanding the Zone Record Template

The Zone Record Template defines the default DNS records applied to every new domain added to Plesk. These records include:

  • A records (IPv4) - An A record maps a domain name to an IPv4 address (e.g., 192.0.2.10). It’s one of the most fundamental DNS records and is required for pointing your domain to a server hosting your website or application.
  • AAAA records (IPv6) - An AAAA record (pronounced “quad-A”) maps a domain name to an IPv6 address (e.g., 2001:0db8::1). It serves the same purpose as an A record but for modern IPv6-enabled servers and networks.
  • MX records - MX (Mail Exchange) records define which mail servers are responsible for receiving email for a domain. They include a priority value, with lower numbers indicating higher priority. Email systems use these records to know where to deliver incoming mail.
  • CNAME records - A CNAME (Canonical Name) record points one hostname to another hostname instead of an IP address. Useful for pointing subdomains (like www.hostarmada.com) to the main domain (hostarmada.com) so you only need to update the IP in one place.
  • TXT records - TXT records store arbitrary text information. Typical uses include SPF (Sender Policy Framework) to define which mail servers are allowed to send email for your domain, DKIM and DMARC verification, and domain ownership verification for services like Google, Microsoft, and Cloudflare.
  • NS (Name Server) Records - NS records specify which nameservers are authoritative for a domain. These nameservers hold all DNS records for the domain. If NS records are incorrect, the entire domain’s DNS may fail.
  • SRV records - SRV (Service) records define the location of specific services within a domain, such as SIP servers, Teams/Skype services, Minecraft servers, or LDAP. They specify the service, protocol, priority, weight, port, and target host, and allow applications to discover the correct service endpoints automatically.

When you update the DNS Template, Plesk can automatically apply these changes to existing DNS zones if you choose to synchronize them.

Editing DNS Template Records

To modify the default DNS records, please click on the individual record, which in turn will open a side menu that will allow you to modify it.

select-record

Depending on the record you selected, you can change different parameters of the DNS zone. In our case, we selected the Name Server record; thus, we can update the following:

  • Record Type (A, CNAME, MX, TXT, etc.) - Please use the drop-down menu to select the type of record
  • TTL - Please enter the TTL (Time to Live) for the DNS record in the text field
  • Domain Name - Please use the text field to add the domain name for the DNS record
  • Name Server - Please use the text field to add the name server for the DNS record.

edit-record

Please click “Save” to save your changes.

To add a new record, please click the “+ Add Record” button at the top left of the middle table section, which contains all the DNS record templates.

add-record

Performing the action above will reveal the same side menu as mentioned in the previous paragraph.

Please fill in the required fields and press the “Save” button at the bottom to add a new record.

Finally, to remove a record, please use the tickbox corresponding to the DNS record you want to remove. 

remove-record

Afterward, please press the “Remove” button and confirm the prompt to delete it.

Synchronizing DNS Template With All Domains

After making changes to the DNS Template, you may want to apply them to all existing domains using local DNS. To do that, please locate the “Apply DNS Template Changes” button located above the table section and click on it.

apply-dns-templates

Afterward, please confirm the action so the changes are applied. This ensures that all domains follow the updated DNS configuration.

Managing DNS Server Settings

Depending on your Plesk version, you can also manage global DNS server configuration. To do that, please click on the “Server-wide Settings” tab, located above the table section.

server-wide-settings

Once you are redirected to the “Server-wide Settings” tab, there you will be able to edit the following settings:

 

  • Recursive DNS queries - A recursive DNS query is a type of DNS lookup where the DNS resolver (usually your ISP’s or a public resolver like Google DNS or Cloudflare DNS) is responsible for doing all the work required to find the final answer. Please use the radio buttons here to select the behaviour for recursive DNS queries.
  • Additional DNS settings - Please use the checkbox to add DNS settings for your Plesk Server. Essentially, this is a visual interface representation of the named. In the conf file, using the same syntax, you can add whichever directories you need inside.

apply-dns-settings

These settings affect how your server handles DNS queries overall. To save them, please click the “OK” button at the bottom of the page to be redirected to the “Tools & Settings” page, or click the “Apply” button to save the changes and remain on the same page so you can review them and confirm they are correct.

Best Practices for Managing Global DNS Settings

To maintain consistent, secure DNS across your servers, we have compiled a list of practices below that you can refer to and apply. Of course, our recommendations are based on years of field experience and are also used to manage our own servers at HostArmada.

  • Use TXT records to properly configure SPF, DKIM, and DMARC.
  • Keep NS records consistent across your template.
  • Avoid modifying DNS for individual domains unless necessary.
  • Apply DNS Template synchronization after significant changes.
  • Disable DNS for domains using external DNS providers.
  • Use DNSSEC if your registrar and Plesk version support it.

Conclusion

As you can see, Plesk makes it easy to manage global DNS settings using its DNS Template and server-wide DNS configuration tools. By updating your DNS Template and synchronizing changes across domains, you ensure consistency, improve stability, and reduce the chances of DNS misconfiguration.

We hope this tutorial was helpful, and we kindly encourage you to review your DNS settings periodically - especially after adding new services, email systems, or subdomains.

...
Nikola Zgurev
Technical Support Captain

Nikola is an accomplished tech-savvy extraordinaire with over six years of experience in the web hosting field. He started as a customer care representative and quickly rose the ranks to become a support supervisor and, eventually - the head of the technical department in HostArmada. His deep understanding of the client's needs, combined with his technical knowledge, makes him the perfect man to create the ideal harmony between client satisfaction and professional problem-solving. You will often find him creating helpful tutorials, articles, and blog posts that help existing customers get around.