• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Plesk DNS Server

DieterWerner

Regular Pleskian
Could someone please explain the practical sense (advantage) of the Plesk DNS server to me?
Consider that I'm a dork - so please explain it as simple as you can.
 
Last edited:
Internet traffic is divided into packets. Each packet gets an address sticker that tells the network where to deliver the packet to. That address is the IP address. However, users don't want to remember IP addresses, but names. For example domain names. So they type a domain name into their browser. The purpose of DNS is to translate these domain names into IP addresses, so that the packets can be sent over the network through the server and from the server back to the browser.

In your Plesk DNS server you can create A-records, that translate a name into an IP address. Thus you tell other systems, where to send the packets to when someone enters a domain name instead of an IP address. You can also create CNAMES, that's a kind of alias (pseudonym) for a name. And you can create MX records, by which you tell other systems where to send mails to. There are several other types of nameserver records, like TXT, SRV, AAAA (for IPv6) to do a lot more magic.
 
I'm impressed Peter - but sorry, that doesn't answer my question
I understood that you wanted to know what practical use a DNS server has, and have answered that question. Could you please re-phrase the question so that others and me understand better what exactly you would like to know?
 
This sounds more like a general question about using built-in DNS management with control panels -

As it pertains to Plesk, Plesk DNS offers relatively tight integration with the Plesk ecosystem for business models that use it (for basic hosting environments it's a quick and no-cost way to offer DNS within the control panel) however running DNS on the same instance as a Plesk server may not be a best practice as an outage, even if it wasn't specific to the DNS service itself, could stop serving requests for non-Plesk services regardless of their location.

Now Mr. Plesk thought of those use cases and has support for third party DNS services as documented here.
 
Back
Top