hi,
when i tried to start the DNS server after making an internal zone i got this error



Error in named configuration:
zone localdomain/IN: loaded serial 42
zone localhost/IN: loaded serial 42
zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
zone 255.in-addr.arpa/IN: loaded serial 42
zone 0.in-addr.arpa/IN: loaded serial 42
my.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
zone my.internal.zone/IN: loaded serial 1
slaves/my.ddns.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
zone my.ddns.internal.zone/IN: loaded serial 1
zone sunny.internal/IN: loading master file sunny.internal.db: file not found
internal/sunny.internal/IN: file not found
my.external.zone.db:1: no TTL specified; using SOA MINTTL instead
zone my.external.zone/IN: loaded serial 1




my internal zone file is as follow...


$TTL 86400
@ IN SOA VMrhel5.sunny.internal root.VMrhel5.sunny.internal
20111216 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum

IN NS VMrhek5.sunny.internal
VMrhel5 IN A 192.15.1.240



help me to solve this issue...

Does the file exist as named (sunny.internal.db)?
Within the chroot if you are using bind-chroot (/var/named/chroot/var/named/ -- by default)?

i dont understood what u tring to say
explain it deepely

By what name have you configured your internal zone file which you have posted and what is the location of this file?

there can be two places either
match the names of zone files with the names you have mentioned in your configuration file and make sure the file is present at the location where you have put all other zone files.

At a quick glance three points spring to mind:

1. Consider adding another two digits to the end of your serial, so that for the first change of a zone file today would be 2011121601 and if you change it again then it would be 2011121602
2. You have not added a . at the end of your declaration for the NS so that name will be prepended to the zone file, so it will end up defined as VMrhek5.sunny.internal.VMrhel5.sunny.internal
3. Also in your NS declaration do you mean VMrhel5 rather than VMrek5

i m still faceing error

now the error is


Starting named:
Error in named configuration:
zone localdomain/IN: loaded serial 42
zone localhost/IN: loaded serial 42
zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
zone 255.in-addr.arpa/IN: loaded serial 42
zone 0.in-addr.arpa/IN: loaded serial 42
my.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
zone my.internal.zone/IN: loaded serial 1
slaves/my.ddns.internal.zone.db:1: no TTL specified; using SOA MINTTL instead
zone my.ddns.internal.zone/IN: loaded serial 1
dns_rdata_fromtext: sunny.internal.db:2: near eol: unexpected end of input
dns_master_load: sunny.internal.db:4: unexpected end of line
dns_master_load: sunny.internal.db:3: unexpected end of input
dns_master_load: sunny.internal.db:6: unexpected end of line
dns_master_load: sunny.internal.db:5: unexpected end of input
dns_master_load: sunny.internal.db:8: unexpected end of line
dns_master_load: sunny.internal.db:7: unexpected end of input
zone sunny.internal/IN: loading master file sunny.internal.db: unexpected end of input
internal/sunny.internal/IN: unexpected end of input
my.external.zone.db:1: no TTL specified; using SOA MINTTL instead
zone my.external.zone/IN: loaded serial 1
[FAILED]



and my named.conf file is...


//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
// file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//
options
{
// Those options should be used carefully because they disable port
// randomization
// query-source port 53;
// query-source-v6 port 53;

// Put files that named is allowed to write in the data/ directory:
directory "/var/named"; // the default
dump-file "data/cache_dump.db";
statistics-file "data/named_stats.txt";
memstatistics-file "data/named_mem_stats.txt";

};
logging
{
/* If you want to enable debugging, eg. using the 'rndc trace' command,
* named will try to write the 'named.run' file in the $directory (/var/named).
* By default, SELinux policy does not allow named to modify the /var/named directory,
* so put the default debug log file in data/ :
*/
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//
view "localhost_resolver"
{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
# all views must contain the root hints zone:
include "/etc/named.root.hints";

/* these are zones that contain definitions for all the localhost
* names and addresses, as recommended in RFC1912 - these names should
* ONLY be served to localhost clients:
*/
include "/etc/named.rfc1912.zones";
};
view "internal"
{
/* This view will contain zones you want to serve only to "internal" clients
that connect via your directly attached LAN interfaces - "localnets" .
*/
match-clients { localnets; };
match-destinations { localnets; };
recursion yes;
// all views must contain the root hints zone:
include "/etc/named.root.hints";

// include "named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.

// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :

zone "my.internal.zone" {
type master;
file "my.internal.zone.db";
};
zone "my.slave.internal.zone" {
type slave;
file "slaves/my.slave.internal.zone.db";
masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
// put slave zones in the slaves/ directory so named can update them
};
zone "my.ddns.internal.zone" {
type master;
#allow-update { key ddns_key; };
file "slaves/my.ddns.internal.zone.db";
// put dynamically updateable zones in the slaves/ directory so named can update them
};
###my first internal zone###
zone "sunny.internal" {
type master;
#allow-update { key ddns_key; };
file "sunny.internal.db";
};
};
#key ddns_key
#{
# algorithm hmac-md5;
# secret "use /usr/sbin/dns-keygen to generate TSIG keys";
#};


view "external"
{
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
match-clients { any; };
match-destinations { any; };

recursion no;
// you'd probably want to deny recursion to external clients, so you don't
// end up providing free DNS service to all takers

allow-query-cache { none; };
// Disable lookups for any cached data and root hints

// all views must contain the root hints zone:
include "/etc/named.root.hints";

// These are your "authoritative" external zones, and would probably
// contain entries for just your web and mail servers:

zone "my.external.zone" {
type master;
file "my.external.zone.db";
};
};




and my sunny.internal.db file is...


$TTL 600
@ IN SOA VMrhel5.sunny.internal. root.VMrhel5.sunny.internal.
2011121801 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ; minimum

IN NS VMrhel5.sunny.internal.
VMrhel5 IN A 192.15.1.240



help me how to solve this issue........

please use code tags so that it becomes easier to read and understand for us

the error fields as per your config file are marked with re colour

for further help you can follow this link

DNS configuration in RHEL (Forward and reverse zone)