DNS ISSUES connect failed: 127.0.0.1 # 953: connection refused

Hello everyone I am here to bring it to the following problem, after days of failed attempts.
3 Ispconfig3 DNS stopped working, I'm not sure if after updates or not, because the monitor says it all OK.

I tried again to restore in new ISPCONFIG3 Debian6 on VPS with BIND9, works for a while, when you start writing the new areas, it stops working.

I reinstalled a new version of VPS MyDNS, when I recorded the new areas, stopped FunZone, I do not know that connection can be given that does not use BIND9.
Now I am back to the BIND9 version, it worked until I populated areas.
here is the current situation, if you restart

doing debugging ispconfig as indicated in the FAQ,
I found this statement, do you mean by remove locks?
excuse the banality but it is the first time that I have this message.
It refers to the file permissions?
As you can see I have all the DNS right and between the various tests that I am carrying out for 24 hours beginning to have a mess!

The server was not stable, the same tests nslookup give different results, I noticed that by making changes in the records of the areas, are not reflected in the query response in spite of the areas that the file is changed.

Today oddly enough the DNS server that I reinstalled from scratch to work again, except for some areas, I had to re-enter all areas, because if I use the Backup of the database does not work anymore, even if the gate areas and recreate, to I have to rip it to work the process from scratch and then enter the zones.

I can say with some logic that has generated the problem with the update, because I do not know which areas also written correctly on the files of BIND, stop responding, while the second DNS server that I have not reinstalled, still does not work, I noticed that has not completed all the updates, if I repeat the update procedure, the problem arises very own BIND indicating that the reconfiguration has completed.

For those not up to date, I would recommend not to upgrade anything, until this matter is not resolved.

If you can serve the area that I can not run contrary to other abg.yu.it this syntax (example)

I do not know what to do further investigation, if anyone wants to give me directions are very willing to perform the further investigations.

For now move to a different DNS domains.

I thank my readers, though I would have liked to have a confrontation with someone, maybe because of my bad English googloliano or because they are still considered a incopetente, was a solitary walk, I hope to be liked by someone and that I can Help the Holy Spirit.

Just FYI, had similar problem. Move DNS to a new server with new ispconfig master. To have DNS as long as possible I gave the new primary DNS a new IP address and after shutdown the old prime I added old DNS address as a secondary to the new DNS master. In named.conf I defined listen to both addresses. netstat said port 53 listen on both addresses TCP and UDP. Telnet to port 53 worked. After install the DNS slave, it did not sync. Searching quit a day I found the master DNS dis not response on queries to the secondary address not on update request from the slave although port 53 open, but responds fine on his base address.
Seems at least BIND9 does not realy run on secondary IP addresses