Prevent subdomains and domain aliases in the DNS zones belonging to other users in Plesk.
By default, users can create new subdomains and domain aliases in the DNS zones belonging to other users. This means that they can set up Web sites and e-mail accounts which could be used for spamming, fishing or identity theft.
To prevent users from setting up domains and domain aliases in the DNS zones belonging to other users:
1. Go to Settings > Restrict Creation of Subzones (in the DNS group).
2. Select the Do not let users create DNS subzones in other users’ DNS superzones check box.
3. Click OK.
How can I create a Webmin user who can only configure one Apache virtual server or DNS domain?
In the Webmin Servers module.
Create a new user and give him access to only the Apache Webserver module.
After saving, click on Apache Webserver next to the user’s name in the list of Webmin users and use the form that appears to deny him access to everything except one selected virtual server.
Many other modules can also be configured in a similar way to restrict the access of a user to only certain DNS domains, Unix users or mail aliases.
DNS Records for Domain Aliasses not provisioned.
Error
when you Domain Alias to a Domain, and select all appropriate check boxes, no records appear in the zone file. The zone file itself is created, and contains the SOA record. But no other records at all.
Resolution:
1. Download the module DNSManager.php and copy it to folder %plesk_dir%admin\plib\dns
2. Download the modules DomainAlias.php and DomainAliasesManager.php and copy it to folder %plesk_dir%admin\plib\domainaliases
Note : Please backup old module before copying.
The concerned files are available from the following links
ftp://download1.swsoft.com/Plesk/Autoupdate/Windows/8.3.0/128001/DNSManager.php
ftp://download1.swsoft.com/Plesk/Autoupdate/Windows/8.3.0/128001/DomainAlias.php
ftp://download1.swsoft.com/Plesk/Autoupdate/Windows/8.3.0/128001/DomainAliasesManager.php
How can I check to see if DNS is working?
Dont use “ping” to test DNS. Use tools called “nslookup” and “dig”.
Check to see whether or not your registrar is pointing your domain to the correct nameservers. The “whois” information is often wrong, and should not be used. Go to a command prompt/console and enter the command:
nslookup -type=NS yourdomainname.com
If the response does not contain all of the correct name servers, then you should contact your registrar and have them fix it.
Check to see whether a particular server is responding, you can add the server name:
nslookup www.yourdomainname.com ns1.yournameserver.com
If the response has a bunch of ‘root-servers’ that means the server does not know about the domain name and is referring you elsewhere.
To look for a certain record type, like the “MX” record or the “SOA” record, you can use the parameter “-type=MX” or “-type=SOA”.
nslookup -type=MX yourdomainname.com
Reducing DNS bandwidth
*Refresh - 86000 - This is time(in seconds) when the slave DNS server will refresh from the master. This value represents how often a secondary will poll the primary server to see if the serial number for the zone has increased (so it knows to request a new copy of the data for the zone). It can be written as “23h88M” indicating 23 hours and 88 minutes. If you have a regular Internet server, you can keep it between 6 to 24 hours.
There is constant bandwidth usage between primary and secondary(backup DNS) servers. This depends a lot on the Refresh value. If the refresh value is say 3 hours, your secondary server is polling your primary server every 3 hours and updating the cache. Lets assume you have a 1000 zone files, each with 3 hours refresh rate. You can imagine the bandwidth that must be getting used. This is especially true if the servers are on 2 separate physical servers.
An increase in the Refresh rate can effectively reduce bandwidth usage between the primary and secondary server.
BEWARE! Any name or label that appears on either the left or right-hand-side of a resource record that does not have a terminating full stop will have the origin added to the name/label. Missing full stops are one of the most common causes of error in DNS zone files.
