I am setting up a DNS for a small subdomain and I am unable to figure out why named is ignoring my zone file.

Here is my zone file:
---begin /var/named/se.digitalreefinc.com.zone------
[root@se20 named]# cat se.digitalreefinc.com.zone
$TTL 3D
; Information about "forward" domain se.digitalreefinc.com
$ORIGIN se.digitalreefinc.com.
@ IN SOA ns1.se.digitalreefinc.com. hostmaster.se.digitalreefinc.com. (
200912151638 ; serial
86400 ; refresh
7200 ; retry
1209600 ; expiry
1D ) ; minimum
@ IN NS ns1.se.digitalreefinc.com.
se20 A 172.30.4.20
ns1.se.digitalreefinc.com. A 172.30.4.20
localhost A 127.0.0.1
se21 A 172.30.4.21
se22 A 172.30.4.22
se23 A 172.30.4.23
se24 A 172.30.4.24

----------------------------------------------
When I do a named-checkzone, I get the following errors

----begin error messages from named-checkzone-------
[root@se20 named]# named-checkzone localhost se.digitalreefinc.com
se.digitalreefinc.com:4: ignoring out-of-zone data (se.digitalreefinc.com)
se.digitalreefinc.com:10: ignoring out-of-zone data (se.digitalreefinc.com)
se.digitalreefinc.com:11: ignoring out-of-zone data (se20.se.digitalreefinc.com)
se.digitalreefinc.com:12: ignoring out-of-zone data (ns1.se.digitalreefinc.com)
se.digitalreefinc.com:13: ignoring out-of-zone data (localhost.se.digitalreefinc.com)
se.digitalreefinc.com:14: ignoring out-of-zone data (se21.se.digitalreefinc.com)
se.digitalreefinc.com:15: ignoring out-of-zone data (se22.se.digitalreefinc.com)
se.digitalreefinc.com:16: ignoring out-of-zone data (se23.se.digitalreefinc.com)
se.digitalreefinc.com:17: ignoring out-of-zone data (se24.se.digitalreefinc.com)
zone localhost/IN: has 0 SOA records
zone localhost/IN: has no NS records
--------------------------------------------------
Here is my named.conf from the server:
----------begin named.conf-------------------------
[root@se20 named]# cat named.conf
//
// named.caching-nameserver.conf
//
// Provided by Red Hat caching-nameserver package to configure the
// ISC BIND named(8) DNS server as a caching only nameserver
// (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// DO NOT EDIT THIS FILE - use system-config-bind or an editor
// to create named.conf - edits to this file will be lost on
// caching-nameserver package upgrade.
//
options {
listen-on port 53 { any; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
version "Bind";
#allow-query { localhost; };
allow-recursion {127.0.0.1; 172.30.0.0/16; };
forward first;
forwarders { 172.30.0.10; 172.30.0.11; }; #IP of upstream ISP nameserver(s)
#forward only; #rely completely on our upstream nameservers
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "." IN {
type hint;
file "named.ca";
};
zone "se.digitalreefinc.com" IN {
type master;
file "se.digitalreefinc.com.zone";
allow-update {none;};
};
zone "4.30.172.in-addr.arpa" IN {
type master;
file "reverse.se.digitalreefinc.com.zone";
allow-update {none;};
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update {none;};
};
include "/etc/named.rfc1912.zones";

--------------------------------------------------

finally, doing a dig gives me an NXDOMAIN error (undoubtedly because the zone file never loaded, as evidenced by my /var/log/messages)

I have been banging my head against this wall for about 2 days and I am sure it is something stupid which I have missed. Thank you in advance for your greatly appreciated assistance.

Did you see the answer at your same post here?

1 members found this post helpful.

Ug, I thought it didn't post as I could find it even via search... so I double posted. Thank you Bathory.