make sure both sides of your zone . malice.homedns.org 799* have the malice.homedns.org it should look kinda like
zone . malice.homedns.org 7995 malice.homedns.org
zone . malice.homedns.org 7996 malice.homedns.org
etc etc
if you specify an outside ip/host for one, you have to do it for both, or else anyone who tries to connect to your computer will crash out with odds and ends errors, espically if it looks like
zone . malice.homedns.org 7995 127.0.0.1
because when the world passes it to the zone, the zone will send THEM (the client program) the command to load zone at 127.0.0.1 which if you dont know is the localhost command, the computer itself, meaning your system on zoneload is telling the client to load the zone from its self machine, the machine the client is running on....
this for the most part is only speculation(I'm not a programer), but its what fixed the troubles I had on my server, and now only a couple people have troubles, and its usually when trying to go into zones that I have had prior zoneserver disconnects when loading, so its really nothing that worries me, as I am sure that my little piddly error will get fixed on the next update
Hope it helps, if not, sorry to have bothered your time
Threaded Mode
