As I said, there's nothing obviously wrong with either file (the [code]
tags helped make that clear), but the output from nslookup
clearly shows that the server is unaware of the existence of the "example.com" zone/domain.
Did you restart named
(BIND) after creating the zone? (Try killall -HUP named
if you haven't; that should force the DNS server to reload its configuration.)
In which directory does example.db
Have you tried starting named
from the command line in foreground mode? Stop named
and run the following command as root:
named -g 2>&1 | grep example.com
Press Ctrl-C once the server has finished loading and post the output here. (And remember to restart named
, of course.)
By the way, which distribution are you using?