MyDNS rude awaking

Ok I have been running myDNS for a couple of months now with no problems. However yesterday we had a server crash that was running MyDNS. It was not MyDNS fault a NIC went bad. That stopped DNS though since we have a slave DNS server running BIND I thought all was well. I had entered in Zone Transfers the approiate IP and since things were working great before switching to MyDNS I just assumed things were working. They were not.

Here are some of the error messages I am getting in the logs of the slave box.

The secondary DNS is trying to get the zones from the primary, but this doesn't work because it's down.
Repair your primary DNS server and boot it, and these errors should go away.
For now, you can ignore them.

Yes that is the IP of the primary DNS, the other server is not on the same subnet. The primary machine is acting as a firewall with 3 interfaces the internet, the LAN and a DMZ. The slave DNS is in the DMZ connected via a cross over cable. The 192.168.1.122 IP is the internet interface of the primary DNS. On the LAN interface there is a caching DNS server running.