A domain name serves as the human-readable internet address for a website, enabling users to access it easily. The Domain Name System (DNS) is responsible for translating these human-readable names into machine-readable IP addresses. Accurate DNS settings are crucial for the uninterrupted operation of your online services. Incorrect configurations can lead to service disruptions, such as your domain becoming inaccessible or email delivery failures. Plesk offers the flexibility to function as either a primary or secondary name server for your domains. While DNS settings are initially configured automatically, they can be conveniently modified through the Plesk interface. Furthermore, if your domain's DNS service is handled by external third-party name servers, you have the option to disable the DNS service within Plesk.
Adding and Modifying DNS Records
Note: This section is intended for advanced users. Incorrectly configuring DNS settings can significantly impact website accessibility and mail delivery, so caution is advised.
Upon the creation of each new domain name, Plesk automatically establishes a DNS zone, adhering to the default settings provided by your service provider. Typically, domain names will function correctly with this automatic configuration. However, for users utilizing Plesk as their authoritative name server who require custom modifications within the domain name zone, these adjustments can be easily performed directly from your Plesk control panel.
To inspect the resource records within a domain's DNS zone, navigate to the Websites & Domains section, and then select DNS Settings.
Should you need to add a new resource record to the DNS zone, proceed to Websites & Domains > DNS Settings, and then click the Add Record button.
To modify the existing properties of a specific resource record, navigate to Websites & Domains > DNS Settings and simply click on the record you wish to edit.
Beyond the standard resource records detailed previously, a crucial component is the Start of Authority (SOA) record. This record unequivocally identifies a particular DNS name server as authoritative for the domain's DNS zone. Furthermore, the SOA record encompasses various settings that govern the propagation and caching of information related to the DNS zone throughout the broader Domain Name System, playing a vital role in how DNS changes are disseminated.
Using External DNS Servers
For users hosting websites on their Plesk account who prefer not to utilize Plesk as their primary DNS server, several alternative configurations are available:
- Use Plesk as a Secondary Name Server: Select this option if you already have a standalone name server that functions as the primary authoritative DNS server for your websites. Plesk will then act as a backup, providing redundancy.
- Disable DNS Service in Plesk: Opt for this choice if your websites are managed by entirely external primary and secondary name servers that hold full authority for your domain's DNS records. This prevents conflicts and ensures external control.
To configure the Plesk DNS server to operate as a secondary name server, navigate to Websites & Domains > DNS Settings, and then click on the Switch to Secondary button.
Conversely, to restore the Plesk DNS server to its role as the primary name server, return to Websites & Domains > DNS Settings and click the Switch to Primary button.
Finally, to completely deactivate Plesk's DNS service for a domain whose DNS records are managed by external name servers, access Websites & Domains > DNS Settings and select the Disable option. This ensures that Plesk will no longer attempt to manage DNS for that specific domain, relying entirely on your external configuration.
