Plesk DNS named.conf Issue – Zone file and corresponding record in named.conf are missed for particular domain
The following tutorial will guide you through the cause and resolution for solving Plesk DNS issues with any domain accounts that are not resolving properly.
Resolution: Editing the Plesk DNS zone database Please note: to isolate database issues with Plesk and your own web services (MySQL or MS SQL), we recommend and setup Plesk to use MS Access databases. If you have setup Plesk to use MySQL or MS SQL databases you will need to use your preferred database viewer to find the necessary DNS zone table. You can view MS SQL instructions below.
- To view and edit the Plesk DNS zone database you will need to use an MS Access database viewer such as MDBPlus, and then open up the pleskmain.db located at:
C:\Program Files (x86)\Parallels\Plesk\admin\db – Note: password is the same as Plesk admin login.
- Check dns_zone records for the problem domain’s entry (domain.com for example):
- if there are multiple entries for the same domain; remove the entry that has the incorrect setting of 2;
- if there is only one entry for the domain, adjust the value in the “status” column from 2 back to 0.
- Save the database.
- Go back into Plesk and navigate to the DNS zone settings tab for the affected domain.
- Select “Restore Defaults” to rebuild the appropriate entries for the domain
You should now be able to resolve the domain correctly.