If I have read your information correctly you have three AD DCs all running DNS using only one DNS zone.
For this to work the server that was initially configured to host DNS should be the authoritative (or master) server for the zone. All other DNS servers should be considered secondary for the zone. (some things change if you have opted to run with integrated DNS)
What may be occuring is that the servers have not correctly registered with the master DNS server.
In the DNS configuration make sure that whichever one was the inital DNS is indicated as the master for the zone and that the other two servers are indicated as secondary. The DNS configuration on the other two servers should indicate that they are secondary servers to the master.
If all of this is correct then make sure the settings for the zone on the master is configured to allow dynamic updating.
(NOTE:One issue to look out for here is that Microsoft DNS does not automatically make a reverse lookup zone when the primary forward zone is created. If you do not see a reverse lookup zone for the IP range of your network then you need to create one and make sure it is also set for dynamic updating keeping in mind which is master and which are secondary servers.)
If every thing looks to be in place then you will need to force the servers to register with the DNS. [its suppose to be automatic but I've found it doesn't always work on servers]
You do this by entering the following in a command window on each server.
IPCONFIG /REGISTERDNS
Make sure to do this on the master server first.
You can tell if it worked if you see entries in the reverse zone appear that look like the one in your error message (after GUID:). If you don't see this within a few minutes then reboot the server.