[Info] Slave DNS servers configured in ‘Transfer Restrictions’ do not receive copies of DNS zones from the server

[Info] Slave DNS servers configured in ‘Transfer Restrictions’ do not receive copies of DNS zones from the server.
SYMPTOMS
After switching the default DNS server in Plesk from BIND to Microsoft DNS not all of the slave DNS servers configured in ‘Transfer Restrictions’ receive copies of DNS zones from the server.
CAUSE
Microsoft DNS doesn’t allow adding subnets to the transfer restrictions list (ACL), as such, 256 IP addresses from each subnet configured in Transfer restrictions in BIND will be added to MS DNS.
RESOLUTION
It is not recommended to allow transfers to all IPs from /8 and /16 networks (2^24 and 2^16 IP addresses) to DNS transfers as it may cause possible security issues. Consider using explicit restrictions for each individual slave server.

[Info] What happens to IP masks in `Transfer restrictions` configuration when Plesk default DNS server is switched from BIND to Microsoft DNS?

[Info] What happens to IP masks in `Transfer restrictions` configuration when Plesk default DNS server is switched from BIND to Microsoft DNS?
RESOLUTION
Microsoft DNS server does not support IP masks. Therefore when you switch from BIND to MSDNS, the masks are transformed into IP addresses. The IP masks /8 and /16 contain too many IP addresses, support of such list would demand significant resources from a server, therefore such masks are transformed to mask /24.
Keywords: IP masks MS DNS Transfer restrictions BIND

[FIX] DNS management page takes long to open

[FIX] DNS management page takes long to open.
CAUSE
The most probable reason is the large amount of IP masks in Transfer restrictions section. Loading long lists of IP addresses can take long.
RESOLUTION
To speed up the process, try decereasing the number of IP masks in the Transfer restrictions section by replacing them with separate IP addresses.
Keywords: MS DNS server slow

[FIX] Refresh function stopped working for one or more domain after switching Plesk defauls DNS server to Microsoft DNS.

[FIX] Refresh function stopped working for one or more domain after switching Plesk defauls DNS server to Microsoft DNS.
CAUSE
Most probably, the reason is in Transfer Restrictions. IP masks /8 and /16 are transformed into /24, therefore zone transfer may be denied for some servers.
RESOLUTION
To fix this issue IP addresses of these servers need to be added into Transfer Restrictions.
Keywords: MS DNS refreshing not working

[Info] Is it possible to change TTL SOA records in all domain zone files?

[Info] Is it possible to change TTL SOA records in all domain zone files?
RESOLUTION

Yes, it is possible to change the

- TTL
- Refresh
- Retry
- Expire
- Minimum

records by updating the `dns_recs` table in the psa database:

If these parameters are absent, the default settings are be used.

Example:

UPDATE dns_recs SET val=”900″ WHERE type=”SOA” AND host=”TTL”;

After updating the records you will need to rebuild all of the domain zone files by running the following command:

“%plesk_bin%\dnsmng” update *
Keywords: SOA TTL DNS records change

[Info] Microsoft DNS server creates an NS record for server’s hostname. What is it needed for?

[Info] Microsoft DNS server creates an NS record for server’s hostname. What is it needed for?
RESOLUTION
This record is created by Microsoft DNS server by default,. It points to your server using server’s host name. If your server’s hostname is not FQDN (Fully Qualified Domain Name) then it may cause problems with domain registration and management. To avoid these problems you need to properly configure the server’s hostname.

It has to meet the requirements for Fully Qualified Domain Name (FQDN):

1. Be able to correctly resolve in DNS. 2. Have a correct PTR DNS record.

It can be verified at http://www.dnsstuff.com

1. DNS lookup form , > Input your server name > Check A record.

The DNS tool should return an IP address of your server.

2. Reverse DNS lookup form > Input that IP address where your server name is resolved > Click on RevDNS button.

The DNS tool should return the full name of your server.

Please refer to the following article for more information:
http://support.microsoft.com/kb/814591/en-us
Keywords: MS DNS same as parent folder) Name Server (NS) server hostname

[FIX] DNSmng.exe fails during domain creation

[FIX] DNSmng.exe fails during domain creation
SYMPTOMS
When creating a new domain Plesk returns the following error:

dnsmng::update() failed: dnsmng failed: Empty error message from utility.
CAUSE
Most probably configuration files of DNS server are corrupted.
RESOLUTION
You can try fixing it using Plesk command line tool:

“%plesk_bin%\defpackagemng.exe” –fix –type=dnsserver

“%plesk_bin%\DNSMng.exe” update *

Note: One more possible reason is the memory shortage, so please check server resources as well.

[FIX] dnsmng.exe displays an error on DNS changes when SimpleDNS is selected as default DNS server is Plesk

[FIX] dnsmng.exe displays an error on DNS changes when SimpleDNS is selected as default DNS server is Plesk.
SYMPTOMS
Any changes made in Plesk with regards to DNS result in the following error:

The process cannot access the file because it is being used by another process. (Error code 32) at Open file ‘C:\Program Files\Simple DNS Plus\data\boot’ at (VFile::open line 87) at execute “C:\Program Files\SWsoft\Plesk\/admin/bin/dnsmng” update domain.com without reverse(vconsoleapp::run line 138) Execute file name: d:\Program Files\SWsoft\Plesk\admin\bin\DNSMng.exe
RESOLUTION

This problem has been solved in Plesk version 8.1.1. Consider upgrading Plesk to the latest version.
ATTACHED FILES:
SimpleProv.zip : http://kb.swsoft.com/attachments/1543/SimpleProv.zip

[FIX] MS DNS and Plesk synchronization works slowly

[FIX] MS DNS and Plesk synchronization works slowly.
SYMPTOMS
Every time DNS configuration is updated in Plesk it takes long to synchronize with MS DNS and Plesk control panel hands during synchronization.
CAUSE
Plesk uses the old mechanism of MS DNS management.
RESOLUTION
This problem has been solved in Plesk version 8.2. Consider upgrading Plesk to the latest version