On 06/26/2011 03:16 PM, Rodrigo Faria Tavares wrote:
> When I tryed to run named, come many messages about bind files not
> exist. Then i put the path each file in /var/named, in
> the /etc/named.rfc1912.zones file. After the changes come this message:
>
> zone localhost/IN: loading from master file /var/named/localhost.zone
> failed: invalid file
This and the other files that you mention should exist and be valid
zone files for the zones they are supposed to serve. Sample localhost.zone:
$TTL 1D
@ IN SOA @ rname.invalid. (
0 ; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
NS @
A 127.0.0.1
AAAA ::1
> Then I created links for chroot.
Make a copy of the zone files inside the chroot, rather than just linking.
Also, pay attention to selinux. If it its not properly configured for your
chroot it will make your life sour and miserable until you just disable it
and be done with it.
> For each file in /var/named come these logs:
> Error in named configuration:
> zone localdomain/IN: loading from master
> file /var/named/localdomain.zone failed: invalid file
To me it looks as if the file is there and bind can read it, but the contents
of the file are incorrect.
Then again, that's not fatal:
> zone localdomain/IN: not loaded due to errors.
"Zone not loaded" means that your server won't answer queries for this zone,
but it will still answer queries for any other zones that were correctly
configured and loaded.
Depending on your distribution, this might be helpful:
http://webhostingneeds.com/Zone_localdomain_IN_loading_master_file_localdomain_zone_file_not_found
Z
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
