Applicable to:
- Plesk for Windows
Symptoms
-
DNS zones served by Bind DNS server on Plesk for Windows are not synced with the slave DNS, configured in Extensions > My extensions > Slave DNS manager ;
-
The correct slave DNS server IP address is configured in DNS Template > Transfer Restrictions Template ;
-
%plesk_dir%/dns/etc/named.conf
has the following lines:CONFIG_TEXT: acl common-allow-transfer {
none;
}; -
Slave DNS server with info logging enabled shows the following error:
CONFIG_TEXT: general: info: zone example.com/IN: Transfer started.
xfer-in: info: transfer of 'example.com/IN' from 203.0.113.2#53: connected using 192.0.2.2#35633
xfer-in: error: transfer of 'example.com/IN' from 203.0.113.2#53: failed while receiving responses: REFUSED
xfer-in: info: transfer of 'example.com/IN' from 10.39.5.12#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.001 secs (0 bytes/sec)
Cause
Plesk bug with id #PPPM-7521: DNS zone Transfer Restrictions Template does not work on Windows with Bind
Resolution
As a workaround, required records might be inserted into Plesk database manually:
-
Connect to the server via RDP ;
-
Run the following query to add slave DNS server to allowed:
C:\> plesk db "REPLACE INTO misc VALUES ('DNS_Allow_Transfer0', '192.0.2.2');"
Note: The second value in the query is the slave DNS IP. It must be the same as in Extensions > My Extensions > Slave DNS Manager.
Note: multiple slave servers can be specified divided by a semicolon:
REPLACE INTO misc VALUES ('DNS_Allow_Transfer0', '192.0.2.2; 192.0.2.3');
-
Reconfigure DNS records:
C:\> plesk repair dns -y
-
Navigate to Extensions > My Extensions > Slave DNS Manager, select slave DNS server and click on Resync.
Comments
0 comments
Please sign in to leave a comment.