I lost power to my server last night in a power outage.
Today the DNS Server doesn't seem to be working. I verified that my server's IP is the primary name server on the clients, however all lookups are going to the secondary (public) name server and therefore giving the public IP address for LAN services.
To test it, I typed in Terminal (both on a client machine and on the server itself) "nslookup [myinternaldomain.com] [mydnsserverip]" and get ";; connection timed out; no servers could be reached"
When I load up Server Admin, I see that the DNS service is running but for Start Time it says "Not Available".
Tried stopping and starting the service.
Yeah; your DNS server isn't running. You'd see some "named" processes if it was.
In OS X Server 10.6.8 in Server Admin.app (unlike in various newer versions ), you can crank up the DNS debugging level through the GUI. Do that. Launch Server Admin.app, select the server, select DNS, select settings, and set the DNS log level settings to "debug", and see if you can get something more logged.
The default DNS log file can be found and displayed via Console.app (Applications > Utilities) or from Terminal.app via the /Library/Logs/named.log file.
You might also find some relevant errors in /var/log/system.log file, depending on why the DNS startup is cratering.
Console.app can also show you a mass of messages, and you might also see where named is encountering error(s). If it's the usual crash-restart schtick, you'll get the same block of restart message(s) logged in the Console.app messages every five or ten or fifteen seconds; whatever the restart interval for the DNS server.
Though it's a little late here, I'd generally recommend configuring a less-interruptible power supply — a LIPS, as they're never truly uninterruptible — battery backup — as OS X Server doesn't really like having the power yanked out.