|Domainplus domain management system FAQ|
Through Plesk, a user can customize DNS settings for each domain created. The Plesk administrator can also enable the client to customize his/her own DNS settings; however, it is very important that the client possesses a strong understanding of DNS prior to making any modifications to the DNS settings.
Improper setup of DNS results in improper functioning of your web, mail and ftp services.
There are five types of accessible DNS records:
A = Address - This record is used to translate host names to IP addresses.
CNAME = Canonical Name - Used to create additional host names, or aliases, for hosts in a domain.
NS = Name Server - Defines an association between a given domain name and the name servers that store information for that domain. One domain can be associated with any number of name servers.
MX = Mail Exchange - Defines the location of where mail should be delivered for the domain.
PTR = Pointer - Defines the IP address and host name of individual hosts in the domain. Translates IP addresses into host names.
When you first enter this screen, you see the DNS status for the domain, as well as the default DNS settings created for the given domain. Plesk will retrieve the default DNS settings from those set up under the Server -> DNS option.
In order to change DNS settings, follow these steps:
From the DNS Settings page, you can switch the DNS zone type from master to slave.
To switch the DNS zone, follow these steps:
To restore the DNS zone by the DNS template, you can select the IP address from the drop-down list to be set up in the template, add the www prefix if required, and click on the Default button to restore it.
A hosting company (we'll use abcdehosting.com, which is for example purposes only, and is not intended to represent any existing companies or domains) wishes to set up their Plesk enabled server as the primary DNS server for all the domains they create and will run secondary DNS services on an external server (the recommended configuration). The Plesk enabled server has an IP address of 10.10.10.1 and the external name server has an IP address of 10.10.10.2. These addresses will be used for ns1.abcdehosting.com and ns2.abcdehosting.com respectively. IP address 10.10.10.1 is also the main server IP address that was set up during Plesk installation.
All name servers need to be properly registered. They need to specifically be registered as name servers with Internic. Also, all domains must be registered with the appropriate name server information.
*The first step in the process is to create the domain abcdehosting.com on the server. By default, when a domain is initially created, even before hosting has been configured, Plesk sets up a DNS record for the domain. This DNS record is created based on the DNS template that is created by the Administrator under the Server -> DNS option. For the purpose of this example we will use the default setup prior to any modifications made by the Administrator under the Server -> DNS option. With this default setup a properly registered domain will resolve. However the setup does require some modification. The initial assumptions are that the DNS, Mail and FTP services are to be handled locally. So the resulting default DNS settings for domain abcdehosting.com are as follows:
*The next step is to create A records for the name server names you will be using. Every name server name must have a specific IP Address associated with it. Manipulate the DNS records for abcdehosting.com to reflect the following. Exact instructions for adding and removing DNS records are described earlier in the section or can be found by selecting Help within Plesk.
No other entries are needed.
*From that point on you would only need to change the NS records for each individual domain, such as abcdehosting2.com, to be ns1.abcdehosting.com and ns2.abcdehosting.com and then remove the A record that is created for the default name server (ns.abcdehosting2.com). The result for a different domain, abcdehosting2.com, would be as follows:
This would be repeated for all the domains created on the server.
Plesk creates the Primary Zone Files for every domain on the server. It will not create any Slave Zone Files for the secondary DNS. If you plan to setup both primary and secondary name servers locally on your Plesk machine it important to understand that you will technically have no Slave Zone Files. For some registrars this can cause rejection of your domain registration request. It is always recommended that secondary DNS services be run on a separate physical server from the primary.
A hosting company, abcdehosting.com, wishes to run both their primary and secondary DNS services remotely from the Plesk enabled server. They have two name servers: ns1.anameserver.com and ns2.anameserver.com. Their Plesk enabled server has the IP-Address of 10.10.10.1.
By default, when a domain is created in Plesk, it is assumed that DNS is being resolved locally. In the case described above, abcdehosting.com needs to add in the appropriate NS records within each newly created domain and then turn DNS off for that domain.
*The first step is to modify the default Plesk DNS settings for the new domain, abcdehosting.com, to include the appropriate NS records. The result would be as follows:
*Then select the On/Off button. Plesk will remove the DNS records, however you will still see the records that you had entered as the NS records for the domains. The result would be as follows:
You can then perform a test on these name servers by selecting either of them. Selecting either name server will perform an NSLookup to check for the DNS records for your specific
|back to Table
Partners: Web Site Designers
back to domainplus domain name registration