Applicable to:
- Plesk Onyx for Linux
Symptoms
-
After migration from Plesk 11.0.9 to Plesk Onyx 17.5, Bind DNS service is down on destination server:
# systemctl status named-chroot.service
● named-chroot.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2017-11-08 00:19:56 UTC; 8min ago
Process: 18458 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
Process: 17871 ExecReload=/bin/sh -c /usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 637 ExecStart=/usr/sbin/named -u named -t /var/named/chroot $OPTIONS (code=exited, status=0/SUCCESS)
Process: 18466 ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf (code=exited, status=1/FAILURE)
Main PID: 675 (code=exited, status=0/SUCCESS)
Nov 08 00:19:56 serverhost named-checkconf[18466]: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
Noe2017110503
Nov 08 00:19:56 serverhost named-checkconf[18466]: zone example.com/IN: NS 'ns3.example.com' has no address records (A or AAAA)
Nov 08 00:19:56 serverhost named-checkconf[18466]: zone example.com/IN: NS 'ns4.example.com' has no address records (A or AAAA)
Nov 08 00:19:56 serverhost named-checkconf[18466]: zone example.com/IN: not loaded due to errors. - On Plesk 11.0.9 there is an NS record ns3.example.com, but ns3.example.com doesn't have A record.
Cause
Plesk Migrator bug #PMT-4096
Resolution
Add 'A' record(s) for all corresponding 'NS' records reported in the error message.
To add a custom DNS record to the domain's DNS zone, go to Websites & Domains > DNS Settings > Add Record .
For additional information refer
Plesk documentation
.
Comments
0 comments
Please sign in to leave a comment.