Solving Plesk DNS Issues - named.conf
Posted by Sean Syed on 20 February 2013 06:24 PM
Plesk DNS named.conf Issue - Zone file and corresponding record in named.conf are missed for particular domain.
Bind DNS server is used. There is no entry in named.conf for some domains, there also no zone file for it in the %plesk_bin%dns\var folder. If records are created manually they will be removed the next time Plesk updates named.conf.
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.
When the DNS zone for a domain is managed via Plesk, the status for this domain in the dns_zone table of the database is temporarily set to a value of 2 (to lock it for any further changes) and is then set back to a value of 0 value when the changes are processed. If for some reason the process is interrupted (Plesk restarts for example) the status field value may not get changed back to 0 and stays as 2. Therefore any changes are no longer recorded until the status is changed back to 0.
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.
You should now be able to resolve the domain correctly.